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/analyzing-authenticode-signaturesReverse engineering e fuzzing

analyzing-authenticode-signatures

⁨Analyzes Windows Authenticode signatures on PE files: checking for a signature,⁩

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/analyzing-authenticode-signatures

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

FirmaFirmato, ed25519
LZX60i1Zue…Dg2zLTBQ==La CLI controlla lo SHA-256 e la firma prima di scrivere qualsiasi file.
Pacchetto02b64178…6f1bfc89
02b641780720…5a3b6f1bfc894 file · ⁦3.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/analyzing-authenticode-signatures@da7600a

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

When to Use

  • You need to know whether a PE is signed and whether the signer is trustworthy.
  • You suspect a stolen/abused code-signing certificate or a forged/invalid signature.
  • You are distinguishing legitimately signed software from signed malware.

Do not use "is signed" as "is safe" — adversaries use stolen certs, abuse catalog signing, and append invalid signatures; a valid signature only attests the signer, not benignity.

Prerequisites

  • Access to the PE security directory (Python struct/pefile); on Windows, signtool/PowerShell Get-AuthenticodeSignature for authoritative verification.

Safety & Handling

  • Parse the signature statically; never execute the sample.
  • Keep the sample password-protected at rest and reference it by hash.

Workflow

Step 1: Check for a signature

Read the PE security directory (certificate table). Absent entry = unsigned; present = embedded PKCS#7. Note that valid signing can also be via a catalog file (not embedded).

bash
python scripts/analyst.py check sample.exe

Step 2: Extract signer details

Parse the PKCS#7 to read the signer certificate: subject, issuer, validity dates, and serial. Cross-reference against known-abused/stolen certs.

Step 3: Verify, do not just read

On Windows, verify the signature cryptographically and check revocation (Get-AuthenticodeSignature). A present-but-invalid signature is a strong red flag.

Step 4: Assess trust in context

Weigh signer reputation, certificate age, and whether the signed file's behavior matches the purported publisher. Treat anomalies (recently issued cert, mismatched publisher) as suspicious.

Validation

  • Signature presence is determined from the security directory, and verified (not just read) on Windows.
  • Signer certificate details are extracted and checked against abuse intel.
  • The trust conclusion accounts for revocation/validity, not mere presence.

Pitfalls

  • Equating a present signature with safety; stolen-cert malware is common.
  • Missing catalog-signed files by only checking embedded signatures.
  • Reading the signature without cryptographically verifying it.

References

  • See references/api-reference.md for the signature checker.
  • Authenticode format and the PE/COFF security directory (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 2026da7600a02b64178Firmata–

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