unpacking-upx-and-common-packers
Identifies and unpacks packed binaries: detecting packers from section names and
v1.0.03 instalações+3 em 7 dias24 EstrelasApache-2.0sincronizado há 10 horas
Instalar
Ainda não tem a CLI da NotHoly? Instale primeiro.
$ curl -fsSL https://notholy.com/install.sh | sh$ notholy skills install meltedinhex/unpacking-upx-and-common-packersGrava em ~/.notholy/skills depois de conferir a assinatura e o SHA-256.
AssinaturaAssinado, ed25519
Pacote14408d55…ebe3013d
14408d55fdb9…35e9ebe3013d4 arquivos · 3.4 KBVarreduraMédio2 achados
- Script executável junto com a skillscripts/analyst.py
- Links para domínios externos
Fontegithub.com/meltedinhex/analyst-ai-pack/tree/main/skills/unpacking-upx-and-common-packers@da7600a
Este item ainda não foi escrito no seu idioma, então aparece em English.
Nesta página
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).
Arquivos desta versão
references/11.2 KB
- api-reference.md1.2 KB
scripts/13.0 KB
- analyst.py3.0 KB
- LICENSE340 B
- SKILL.md3.1 KB
Permissões
| Permissão | Declarada | Encontrada na varredura |
|---|---|---|
| Lê arquivos | Não | Não |
| Grava arquivos | Sim | Sim |
| Roda comandos no shell | Sim | Sim |
| Usa a rede | Sim | Sim |
| Usa conectores | Não | Não |
| Controla um navegador | Não | Não |
Achados da varredura
Revisado em 13 de nov. de 2026
- MédiaArquivo · Script executável junto com a skillscripts/analyst.py
- InfoLink · Links para domínios externos
Uma varredura limpa reduz o risco, mas não prova que o pacote é seguro. Leia o que você instala.
| Versão | Publicada em | Commit | SHA-256 | Assinatura | Mudança de permissão |
|---|---|---|---|---|---|
| v1.0.0 | 13 de nov. de 2026 | da7600a | 14408d55 | Assinada | – |
Mais de meltedinhex
Tudo deste publicador- 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
Mais em Análise de malware e ransomware
Ver a categoria- 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
Pergunte tudo o que o seu escopo permite.
Crie a conta, adicione créditos e faça a primeira pergunta no chat ou no terminal.
- 1/3
Crie a conta
Individual ou empresa. Dá para virar empresa depois sem perder saldo nem chaves.
Pessoa físicaEmpresa - 2/3
Adicione créditos
No cartão. Você paga por token, sem assinatura.
$5.00recarga mínima - 3/3
Pergunte
No chat, ou instale o CLI e rode notholy login no terminal.
$ notholy login