unpacking-upx-and-common-packers
Identifies and unpacks packed binaries: detecting packers from section names and
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/unpacking-upx-and-common-packersWrites to ~/.notholy/skills after checking the signature and the SHA-256.
SignatureSigned, ed25519
Package14408d55…ebe3013d
14408d55fdb9…35e9ebe3013d4 files · 3.4 KBScanMedium2 findings
- Executable script shipped with the skillscripts/analyst.py
- Links to outside domains
Sourcegithub.com/meltedinhex/analyst-ai-pack/tree/main/skills/unpacking-upx-and-common-packers@da7600a
On this page
When to Use
- A sample shows high entropy, few imports, or packer section names, and you need the original code for static analysis or RE.
- You want to unpack UPX automatically or manually unpack a custom/modified packer.
- You are preparing a sample for Ghidra/IDA (decompiling packed code is pointless).
Do not use generic unpackers as a guarantee — modified UPX and custom packers defeat
upx -d. Fall back to debugger-based manual unpacking.
Prerequisites
- Packer detection (Detect It Easy, or the bundled section/entropy heuristics).
upxfor standard UPX; x64dbg + Scylla for manual unpacking (see the x64dbg skill).- Isolated lab.
Workflow
Step 1: Detect the packer
python scripts/analyst.py detect sample.binSignals: section names (UPX0/UPX1, .aspack, .themida), high section entropy, a tiny
import table, and a small .text with a large high-entropy section.
Step 2: Try automated UPX unpacking
If standard UPX:
upx -d -o sample_unpacked.bin sample.binIf upx -d fails on a UPX-like sample, the header was likely tampered (e.g. UPX! magic or
version bytes altered) — repair the marker or unpack manually.
Step 3: Manual unpacking for custom packers
In x64dbg: break on VirtualAlloc/VirtualProtect, run until the unpacked region is written
and made executable, find the tail jump to the original entry point (OEP), and dump there.
Step 4: Dump and rebuild imports
Use Scylla to dump the process and reconstruct the Import Address Table (IAT) so the dumped PE loads in a disassembler.
Step 5: Verify the unpacked result
Confirm the dump is a clean PE with a populated import table and readable strings/code.
Validation
- The unpacked file has restored imports and meaningful strings absent from the packed sample.
- Entropy of the unpacked
.textdrops to normal code levels. - The disassembler resolves API calls (IAT rebuilt correctly).
Pitfalls
- Running
upx -don tampered UPX and concluding it is not UPX; check for renamed/edited markers. - Dumping before reaching the OEP, capturing still-encrypted code.
- Forgetting IAT reconstruction, leaving the dump unusable in Ghidra/IDA.
References
- See
references/api-reference.mdfor the packer detector. - UPX and Detect It Easy (linked in frontmatter).
Files in this version
references/11.2 KB
- api-reference.md1.2 KB
scripts/13.0 KB
- analyst.py3.0 KB
- LICENSE340 B
- SKILL.md3.1 KB
Permissions
| Permission | Declared | Found by the scan |
|---|---|---|
| Reads files | No | No |
| Writes files | Yes | Yes |
| Runs shell commands | Yes | Yes |
| Uses the network | Yes | Yes |
| Uses connectors | No | No |
| Drives a browser | No | No |
Scan findings
Reviewed on Nov 13, 2026
- MediumFile · Executable script shipped with the skillscripts/analyst.py
- InfoLink · Links to outside domains
A clean scan lowers the risk but does not prove a package is safe. Read what you install.
| Version | Published | Commit | SHA-256 | Signature | Permission change |
|---|---|---|---|---|---|
| v1.0.0 | Nov 13, 2026 | da7600a | 14408d55 | Signed | – |
More from meltedinhex
All from this publisher- writing-yara-rules-from-reversed-codemeltedinhex/writing-yara-rules-from-reversed-code4
- validating-detections-with-atomic-testsmeltedinhex/validating-detections-with-atomic-tests4
- writing-suricata-and-snort-rulesmeltedinhex/writing-suricata-and-snort-rules3
- writing-sigma-detection-rulesmeltedinhex/writing-sigma-detection-rules3
More in Malware and ransomware analysis
See the category- yara-sigsdariushoule/yara-sigs4
- monitoring-darkweb-sourcesmukul975/monitoring-darkweb-sources3
- deploying-ransomware-canary-filesmukul975/deploying-ransomware-canary-files3
- implementing-honeypot-for-ransomware-detectionmukul975/implementing-honeypot-for-ransomware-detection3
- yaraaeondave/yara3
- testing-ransomware-recovery-proceduresmukul975/testing-ransomware-recovery-procedures3
Ask anything your scope allows.
Create an account, add credits and ask the first question in the chat or the terminal.
- 1/3
Create the account
Individual or company. You can switch to a company later without losing balance or keys.
IndividualCompany - 2/3
Add credits
By card. Pay per token, no subscription.
$5.00minimum deposit - 3/3
Ask
In the chat, or install the CLI and run notholy login in your terminal.
$ notholy login