building-config-extractors
Builds reusable malware configuration extractors by applying a declarative JSON spec
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/building-config-extractorsScrive in ~/.notholy/skills dopo aver controllato la firma e lo SHA-256.
FirmaFirmato, ed25519
Pacchetto9b1e780d…59968f75
9b1e780dfbff…20c059968f754 file · 3.3 KBScansioneMedio2 segnalazioni
- Script eseguibile incluso nella skillscripts/analyst.py
- Link a domini esterni
Sorgentegithub.com/meltedinhex/analyst-ai-pack/tree/main/skills/building-config-extractors@da7600a
Questa voce non è ancora scritta in italiano, quindi è mostrata in un'altra lingua: English.
In questa pagina
When to Use
- You have reversed a family's config format and want a reusable, declarative extractor instead of one-off scripts.
- You need to apply a spec (offset, XOR/base64 layers, field map) to many samples and emit structured, defanged config.
Do not use a spec built for one variant blindly on another — re-verify offsets/keys per variant. This skill reads samples statically and executes nothing.
Prerequisites
- A reversed understanding of the config (location, decode layers, fields) expressed as a JSON spec.
Safety & Handling
- Read bytes statically; defang recovered endpoints in output.
Workflow
Step 1: Write the extraction spec
Define a JSON spec: blob offset/length (or a marker to search), ordered decode layers
(xor with key, base64), and fields (name, offset, length, type: str/u16/u32/ipv4).
Step 2: Run the extractor
python scripts/analyst.py extract sample.bin --spec family.jsonLocates the blob, applies decode layers, parses fields, and defangs URL/IP fields.
Step 3: Validate output
Confirm fields are plausible (valid hosts, ports, IDs); adjust the spec as needed.
Step 4: Reuse
Store the spec per family and apply across the corpus.
Validation
- The spec round-trips on a known sample to the expected config.
- Decode layers are applied in order and produce readable output.
- URL/IP fields are defanged in the emitted config.
Pitfalls
- Hardcoding a variant-specific offset that shifts in other builds — prefer markers.
- Wrong field endianness (
u16/u32little vs big) producing garbage ports. - Forgetting a decode layer (base64 over XOR) and parsing ciphertext as fields.
References
- See
references/api-reference.mdfor the extractor engine. - ATT&CK T1140 and config-extractor framework concepts (linked in frontmatter).
File di questa versione
references/11.5 KB
- api-reference.md1.5 KB
scripts/13.4 KB
- analyst.py3.4 KB
- LICENSE340 B
- SKILL.md2.7 KB
Permessi
| Permesso | Dichiarato | Trovato dalla scansione |
|---|---|---|
| Legge file | No | No |
| Scrive file | No | No |
| Esegue comandi shell | Sì | Sì |
| Usa la rete | Sì | Sì |
| Usa i connettori | No | No |
| Controlla un browser | No | No |
Segnalazioni della scansione
Rivisto il 13 nov 2026
- MediaFile · Script eseguibile incluso nella skillscripts/analyst.py
- InfoLink · Link a domini esterni
Una scansione pulita abbassa il rischio, ma non prova che il pacchetto sia sicuro. Leggi quello che installi.
| Versione | Pubblicata | Commit | SHA-256 | Firma | Cambio di permessi |
|---|---|---|---|---|---|
| v1.0.0 | 13 nov 2026 | da7600a | 9b1e780d | Firmata | – |
Altro da meltedinhex
Tutto da questo editore- 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
Altro in Analisi di malware e ransomware
Vai alla 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
Chiedi tutto quello che il tuo perimetro consente.
Crea un account, aggiungi crediti e fai la prima domanda in chat o nel terminale.
- 1/3
Crea l'account
Privato o azienda. Puoi passare ad azienda in seguito senza perdere saldo o chiavi.
PrivatoAzienda - 2/3
Aggiungi crediti
Con carta. Paghi a token, senza abbonamento.
$5.00ricarica minima - 3/3
Chiedi
In chat, oppure installa la CLI ed esegui notholy login nel terminale.
$ notholy login