CyberKit

Debugging

Also called Debugger.

Controlling a running sample step by step to watch its state.

What it is

Executing a program under a debugger so the analyst can set breakpoints, single-step instructions, and inspect registers and memory as it runs. It bridges static reading and live behavior.

Why it matters

Debugging is how analysts dump decrypted payloads, observe self-modifying code, and confirm what a routine really computes. Malware frequently checks for a debugger and alters its behavior when one is present.

In practice

Setting a breakpoint right after the unpacking stub and dumping the cleartext payload from memory.

What to look for

  • Breakpoints on key APIs such as VirtualAlloc or CreateProcess.
  • Decoded strings and configs in memory.
  • Anti-debugging checks that change behavior.

Common mistake

Debugging live malware on a connected host. Use an isolated VM with snapshots.

Practice it nearby

CyberKit has no tool for this term itself. These are the closest places to practice it.

In the field

Well-known tools where this shows up on the job. They are listed to show the landscape, not as a recommendation.

  • Ghidra Open source

    A disassembler and decompiler for reading what a sample's code actually does. Our notes.

  • YARA Open source

    Writes rules that match a family's code or strings across many files. Our notes.

  • VirusTotal Commercial

    Shows how many engines flag a file, plus its relations to domains and other samples.

  • ANY.RUN Commercial

    An interactive sandbox where you watch a sample run and click through what it asks for.

Tools practitioners use

  • WinDbg: Kernel & user-mode debugging of dumps
  • x64dbg: Open-source Windows debugger

Read next

  • Anti-Debugging: Tricks malware uses to detect or resist analysis under a debugger.
  • Dynamic Analysis: Running a sample under observation to record what it actually does.
  • Disassembly: Translating machine code back into human-readable assembly.

Sources