Skip to content
New

DeepSeek V4.1 Flash free for 7 days: 10M tokens a day after a top-up of $10 or more. Until Nov 30.

How it works
meltedinhex/manually-unpacking-a-packed-binaryReverse engineering and fuzzing

manually-unpacking-a-packed-binary

⁨Manually unpacks a runtime-packed Windows binary by finding the original entry point⁩

v1.0.03 installs+3 in 7 days24 StarsApache-2.0synced 10 hours ago

Install

No NotHoly CLI yet? Install it first.

$ curl -fsSL https://notholy.com/install.sh | sh
$ notholy skills install meltedinhex/manually-unpacking-a-packed-binary

Writes to ⁦~/.notholy/skills⁩ after checking the signature and the SHA-256.

SignatureSigned, ed25519
FV7/yvLeaU…JJPHXfCw==The CLI checks the SHA-256 and the signature before it writes a file.
Packageec3d28e7…eb3caf92
ec3d28e7a7e6…bd0ceb3caf924 files · ⁦3.3 KB⁩
ScanMedium2 findings
  • Executable script shipped with the skillscripts/analyst.py
  • Links to outside domains
See the full scan
Sourcegithub.com/meltedinhex/analyst-ai-pack/tree/main/skills/manually-unpacking-a-packed-binary@da7600a

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

bash
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.md for the inspector.
  • ATT&CK T1027.002 and the PE format spec (linked in frontmatter).

Files in this version

Permissions

PermissionDeclaredFound by the scan
Reads filesNoNo
Writes filesYesYes
Runs shell commandsYesYes
Uses the networkYesYes
Uses connectorsNoNo
Drives a browserNoNo

Scan findings

Reviewed on Nov 13, 2026

  1. MediumFile · Executable script shipped with the skillscripts/analyst.py
  2. InfoLink · Links to outside domains

A clean scan lowers the risk but does not prove a package is safe. Read what you install.

VersionPublishedCommitSHA-256SignaturePermission change
v1.0.0Nov 13, 2026da7600aec3d28e7Signed–

Ask anything your scope allows.

Create an account, add credits and ask the first question in the chat or the terminal.

  1. 1/3

    Create the account

    Individual or company. You can switch to a company later without losing balance or keys.

    IndividualCompany
  2. 2/3

    Add credits

    By card. Pay per token, no subscription.

    $5.00minimum deposit
  3. 3/3

    Ask

    In the chat, or install the CLI and run notholy login in your terminal.

    $ notholy login