Vai al contenuto
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/unpacking-upx-and-common-packersAnalisi di malware e ransomware

unpacking-upx-and-common-packers

⁨Identifies and unpacks packed binaries: detecting packers from section names and⁩

v1.0.03 installazioni+3 in 7 giorni24 StelleApache-2.0sincronizzato 10 ore fa

Installa

Non hai ancora la CLI di NotHoly? Installala prima.

$ curl -fsSL https://notholy.com/install.sh | sh
$ notholy skills install meltedinhex/unpacking-upx-and-common-packers

Scrive in ⁦~/.notholy/skills⁩ dopo aver controllato la firma e lo SHA-256.

FirmaFirmato, ed25519
aVniTClNQK…RI0Ts8DQ==La CLI controlla lo SHA-256 e la firma prima di scrivere qualsiasi file.
Pacchetto14408d55…ebe3013d
14408d55fdb9…35e9ebe3013d4 file · ⁦3.4 KB⁩
ScansioneMedio2 segnalazioni
  • Script eseguibile incluso nella skillscripts/analyst.py
  • Link a domini esterni
Vedi la scansione completa
Sorgentegithub.com/meltedinhex/analyst-ai-pack/tree/main/skills/unpacking-upx-and-common-packers@da7600a

Questa voce non è ancora scritta in italiano, quindi è mostrata in un'altra lingua: English.

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).
  • upx for standard UPX; x64dbg + Scylla for manual unpacking (see the x64dbg skill).
  • Isolated lab.

Workflow

Step 1: Detect the packer

bash
python scripts/analyst.py detect sample.bin

Signals: 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:

bash
upx -d -o sample_unpacked.bin sample.bin

If 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 .text drops to normal code levels.
  • The disassembler resolves API calls (IAT rebuilt correctly).

Pitfalls

  • Running upx -d on 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.md for the packer detector.
  • UPX and Detect It Easy (linked in frontmatter).

File di questa versione

Permessi

PermessoDichiaratoTrovato dalla scansione
Legge fileNoNo
Scrive fileSìSì
Esegue comandi shellSìSì
Usa la reteSìSì
Usa i connettoriNoNo
Controlla un browserNoNo

Segnalazioni della scansione

Rivisto il 13 nov 2026

  1. MediaFile · Script eseguibile incluso nella skillscripts/analyst.py
  2. InfoLink · Link a domini esterni

Una scansione pulita abbassa il rischio, ma non prova che il pacchetto sia sicuro. Leggi quello che installi.

VersionePubblicataCommitSHA-256FirmaCambio di permessi
v1.0.013 nov 2026da7600a14408d55Firmata–

Chiedi tutto quello che il tuo perimetro consente.

Crea un account, aggiungi crediti e fai la prima domanda in chat o nel terminale.

  1. 1/3

    Crea l'account

    Privato o azienda. Puoi passare ad azienda in seguito senza perdere saldo o chiavi.

    PrivatoAzienda
  2. 2/3

    Aggiungi crediti

    Con carta. Paghi a token, senza abbonamento.

    $5.00ricarica minima
  3. 3/3

    Chiedi

    In chat, oppure installa la CLI ed esegui notholy login nel terminale.

    $ notholy login