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/performing-static-pe-analysisReverse engineering e fuzzing

performing-static-pe-analysis

⁨Extracts structure and indicators from a Windows PE file without executing it:⁩

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/performing-static-pe-analysis

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

FirmaFirmato, ed25519
/91FV/v393…5PWEJuBA==La CLI controlla lo SHA-256 e la firma prima di scrivere qualsiasi file.
Pacchettoe5a1e68b…87ce1f6f
e5a1e68bd110…e1bf87ce1f6f4 file · ⁦4.1 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/performing-static-pe-analysis@da7600a

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

When to Use

  • You have a Windows executable or DLL and need to infer its capabilities before (or instead of) detonation.
  • You want to assess packing, suspicious imports, timestamps, and embedded resources.
  • You are gathering features for YARA authoring or detection.

Do not use import tables alone to conclude behavior — packed samples hide imports until runtime. If imports are sparse and entropy is high, move to unpacking.

Prerequisites

  • pefile (pip install pefile) and optionally capa/PEStudio for deeper capability ID.
  • The sample in neutralized form inside the lab.

Safety & Handling

  • Static only: parse the file, never run it. Keep the neutralized extension.

Workflow

Step 1: Parse headers and metadata

bash
python scripts/analyst.py analyze sample.bin

Note the compile timestamp (often forged), subsystem (GUI/console), machine type (x86/x64), and whether it is a DLL.

Step 2: Review sections and entropy

Per-section entropy reveals packing. A tiny .text plus a huge high-entropy section, or non-standard section names (UPX0, .themida), indicate a packer:

text
.text   entropy 6.4  (normal code)
UPX1    entropy 7.95 (packed)

Step 3: Classify imports

Group imported APIs into behavioral buckets:

text
Injection : VirtualAllocEx, WriteProcessMemory, CreateRemoteThread   [T1055]
Network   : InternetOpen, HttpSendRequest, WinHttpConnect            [T1071]
Crypto    : CryptEncrypt, CryptAcquireContext                        [T1486]
Persistence: RegSetValueEx, CreateService                            [T1547/T1543]

A sample importing only LoadLibrary/GetProcAddress is resolving APIs dynamically — a packing/evasion tell.

Step 4: Inspect resources and strings

Look for embedded PEs in resources (droppers), config blobs, and notable strings (URLs, mutex names, paths).

Step 5: Check signing

Verify the Authenticode signature: unsigned, self-signed, or revoked certificates are suspicious for software claiming to be legitimate.

Validation

  • Section entropy and import counts agree (packed → few imports + high entropy).
  • Suspicious import buckets correspond to plausible behavior.
  • Embedded PE detection is confirmed by an MZ/PE header inside a resource.

Pitfalls

  • Trusting the compile timestamp as a real build date — it is trivially forged.
  • Concluding "benign" because imports look ordinary; the import table may be a stub for a packed payload.
  • Ignoring TLS callbacks, which can run code before the entry point.

References

  • See references/api-reference.md for the analyzer and import classification map.
  • Microsoft PE Format spec and pefile (linked in frontmatter).

File di questa versione

Permessi

PermessoDichiaratoTrovato dalla scansione
Legge fileNoNo
Scrive fileNoNo
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 2026da7600ae5a1e68bFirmata–

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