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/writing-yara-rules-from-reversed-codeAnalisi di malware e ransomware

writing-yara-rules-from-reversed-code

⁨Turns reverse-engineering findings into durable YARA detections: selecting stable⁩

v1.0.04 installazioni+4 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/writing-yara-rules-from-reversed-code

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

FirmaFirmato, ed25519
nJ+TtKk+eW…OMyfItBw==La CLI controlla lo SHA-256 e la firma prima di scrivere qualsiasi file.
Pacchetto9590220a…4fe6e79b
9590220a6383…e9244fe6e79b4 file · ⁦3.2 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/writing-yara-rules-from-reversed-code@da7600a

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

When to Use

  • You finished reversing a sample/family and want a detection that survives recompilation and cosmetic changes.
  • You need byte-pattern signatures from decryptors, API-hash constants, or unique algorithms rather than fragile strings.
  • You are converting RE notes into hunting/scanning rules for a corpus.

Do not use volatile artifacts (file paths, mutex names that change per build, packer stubs shared across unrelated families) as your primary anchor — they cause drift and false hits.

Prerequisites

  • The yara engine (and ideally yara-python) for testing.
  • A small corpus: target samples (true positives) and clean/unrelated files (false-positive control).

Workflow

Step 1: Choose stable anchors

Prefer, in order: a unique algorithm's opcode sequence (decryptor, hashing loop), embedded magic constants (API hashes, XOR keys, S-box), then distinctive strings only if intrinsic.

Step 2: Extract byte patterns with wildcards

Pull the relevant opcodes and wildcard volatile operands (addresses, immediates) so the rule survives relocation/recompilation:

text
$dec = { 8A 04 ?? 34 ?? 88 04 ?? 41 3B ?? 7? ?? }   ; xor-decrypt loop, regs/disp wildcarded

Step 3: Assemble the rule

Combine 2–3 independent anchors with a condition requiring enough of them, plus a cheap prefilter (file size, PE magic) to keep scanning fast:

bash
python scripts/analyst.py scaffold --name family_xyz --hash 0xABCDEF12

Step 4: Validate against the corpus

Run the rule across true positives and the clean control set; require all TPs match and zero FPs on the control.

bash
yara -r rules/family_xyz.yar ./corpus

Step 5: Tune and document

Adjust thresholds, add meta (author, date, reference, hash), and record which construct each string anchors so future analysts can maintain it.

Validation

  • Rule matches all intended samples and produces zero hits on the clean control set.
  • Anchors map to intrinsic code/constants, not build-specific noise.
  • meta documents source samples and the reasoning for each pattern.

Pitfalls

  • Wildcarding too little (brittle) or too much (false positives); wildcard only volatile bytes.
  • Anchoring on shared library/packer code present in unrelated binaries.
  • Skipping the clean-corpus test, shipping a noisy rule.

References

  • See references/api-reference.md for the rule scaffolder.
  • YARA documentation and style guide (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 2026da7600a9590220aFirmata–

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