CyberKit

Disassembly

Also called Disassembling.

Translating machine code back into human-readable assembly.

What it is

The process of converting a binary's raw machine-code bytes into the assembly mnemonics that represent each instruction. Every later step in low-level reverse engineering of a compiled sample starts from it.

Why it matters

Reading the disassembly lets an analyst follow exactly what a program does at the instruction level, including logic that obfuscation or stripped symbols would otherwise hide. It underpins signature creation and unpacking work.

In practice

Stepping through the disassembled decryption routine of a packer to recover the plaintext payload.

What to look for

  • Function calls to network, crypto or process APIs.
  • Loops that decode strings or configs.
  • Code paths that only run under certain conditions.

Common mistake

Reading every function. Start from interesting imports and strings and work backward.

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.

  • 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

  • Ghidra: Software reverse-engineering suite
  • Cutter: Reverse-engineering platform built on rizin

Read next

  • Static Analysis: Examining a sample's code and structure without executing it.
  • Control-Flow Flattening: Obfuscation that hides logic behind a dispatcher and state variable.
  • Debugging: Controlling a running sample step by step to watch its state.

Sources