meltedinhex/analyst-ai-pack / skills/manually-unpacking-a-packed-binary
manually-unpacking-a-packed-binary
VerifiedManually unpacks a runtime-packed Windows binary by finding the original entry point (OEP) through tail-jump and entropy analysis, then guiding a memory dump at OEP. Activates for requests to manually unpack a sample, find the OEP, or unpack a custom/unknown packer that generic tools cannot handle.
Manually Unpacking a Packed Binary
When to Use
- A sample is runtime-packed by a custom/unknown packer that UPX and generic unpackers cannot handle.
- You need to locate the original entry point (OEP) and dump the unpacked image for static analysis.
Do not use generic auto-unpackers here — this is the manual path for cases where they fail. Run the sample only inside an isolated, instrumented debugger VM.
Prerequisites
- A debugger (x64dbg) on an isolated VM and the packed sample.
Safety & Handling
- The sample executes during unpacking; do this only in a disposable, isolated VM with snapshots.
Workflow
Step 1: Characterize the packer statically
python scripts/analyst.py inspect packed.exe
Reports section entropy, suspicious section names (UPX, .vmp, random), small import tables,
and a write-then-execute section (classic unpacker stub).
Step 2: Find candidate OEP heuristics
Set a memory breakpoint on the unpacked code section's execution; the packer's tail jump (a far
jmp/ret into a different section) typically transfers control to the OEP.
Step 3: Dump at OEP
When stopped at OEP, dump the process image and proceed to import reconstruction (see the dump-and-rebuild skill).
Step 4: Verify the dump
Confirm the dumped image has a sane entry point, restored imports, and readable code.
Validation
- The unpacking stub is identified by a write→execute section transition.
- The tail jump lands in a different section than the stub (OEP candidate).
- The dumped image disassembles cleanly with recognizable runtime startup code.
Pitfalls
- Stopping at a stage-2 stub rather than the true OEP in multi-layer packers.
- Hardware-breakpoint detection by the packer — vary the breakpoint strategy.
- Dumping before the import table is fully resolved.
References
- See
references/api-reference.mdfor the inspector. - ATT&CK T1027.002 and the PE format spec (linked in frontmatter).
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| slack-gif-creatoranthropics/skillsKnowledge and utilities for creating animated GIFs optimized for Slack. Provides constraints, validation tools, and animation concepts. Use when users request animated GIFs for Slack like "make me a GIF of X doing Y for Slack." | Stars: 196k | Updated | Claude CodeCodex | Verified | Install |
| ponytailDietrichGebert/ponytailLazy senior dev mode for any coding task: the smallest change that fully solves it, and a reply a busy human understands in one read. | Stars: 193k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailHarvest every shortcut: comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot report. | Stars: 193k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailList every `shortcut:` comment (and older `ponytail:` ones) as a debt ledger. One-shot report, changes nothing. Use for "ponytail debt", "what did ponytail defer", "list the shortcuts", /ponytail-debt. | Stars: 193k | Updated | Claude CodeCodex | Verified | Install |