CyberKit

Manual Unpacking

Also called Hand unpacking.

Reversing a packer by hand to recover the real payload.

What it is

The process of defeating a packer interactively (typically under a debugger) by running its stub, locating the original entry point where the genuine code begins, and dumping the reconstructed payload from memory. It is used when no automated unpacker exists.

Why it matters

Custom and updated packers routinely break automated tools, so manual unpacking is the fallback that lets analysis proceed against fresh or bespoke samples. The recovered payload is what real signatures and indicators come from.

In practice

Hand-unpacking a sample with a custom packer by tracing to its original entry point and rebuilding the import table on the dump.

What to look for

  • The original entry point reached after the unpacking stub.
  • A clean PE written to memory after decryption.
  • Import tables rebuilt after dumping.

Common mistake

Dumping memory too early. Wait until the payload is fully unpacked before you dump it.

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.

Read next

  • Crypter: A tool that encrypts a payload and decrypts it in memory at runtime.
  • Debugging: Controlling a running sample step by step to watch its state.
  • Import Address Table: The table the loader fills with addresses of imported functions.

Sources