enriching-iocs-with-threat-intel-sources
Enriches indicators with context from threat-intel sources: planning lookups against
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/enriching-iocs-with-threat-intel-sourcesScrive in ~/.notholy/skills dopo aver controllato la firma e lo SHA-256.
FirmaFirmato, ed25519
Pacchetto0701b45f…f8c9142f
0701b45f781d…8532f8c9142f4 file · 3.0 KBScansioneMedio2 segnalazioni
- Script eseguibile incluso nella skillscripts/analyst.py
- Link a domini esterni
Sorgentegithub.com/meltedinhex/analyst-ai-pack/tree/main/skills/enriching-iocs-with-threat-intel-sources@da7600a
Questa voce non è ancora scritta in italiano, quindi è mostrata in un'altra lingua: English.
In questa pagina
When to Use
- You have atomic indicators and need context: reputation, related infrastructure, first/last seen, and known associations.
- You are scoring indicator confidence before acting or reporting.
- You must plan lookups without leaking your investigation to the adversary.
Do not use active interaction (visiting a C2 URL, resolving a live domain from your own network) for enrichment — use passive sources to avoid tipping off the adversary.
Prerequisites
- Defanged indicators (from the defanging skill) and access to enrichment sources/APIs.
- Awareness of each source's operational-security implications.
Safety & Handling
- Prefer passive sources (passive DNS, sample DBs, reputation feeds) over active probing.
- Never submit a customer/internal sample to a public sandbox without authorization — it becomes publicly retrievable and can expose sensitive data.
Workflow
Step 1: Group indicators by type
Separate hashes, domains, IPs, and URLs; each maps to different enrichment sources.
Step 2: Plan the right lookups
Map each type to passive sources: hashes → sample/AV databases; domains → passive DNS, WHOIS, reputation; IPs → ASN/geo, passive DNS, reputation; URLs → URL reputation/sandbox history.
python scripts/analyst.py plan iocs.jsonStep 3: Score confidence
Combine source agreement, age, and prevalence into a confidence score; a single hit on one feed is weaker than corroboration across independent sources.
Step 4: Annotate and pivot
Attach context (first seen, related infrastructure, family) and pivot on strong links (shared registrant, hosting, certificate) to expand the picture.
Step 5: Record provenance
Note which source provided each piece of context and when, so the enrichment is auditable and re-checkable.
Validation
- Each indicator is routed to type-appropriate, passive sources.
- Confidence reflects corroboration across independent sources, not a single feed.
- Every enrichment carries source and timestamp provenance.
Pitfalls
- Actively resolving/visiting live infrastructure and alerting the adversary.
- Uploading sensitive samples to public services, leaking data.
- Treating one feed's verdict as ground truth without corroboration.
References
- See
references/api-reference.mdfor the lookup planner. - MITRE ATT&CK and passive-DNS enrichment concepts (linked in frontmatter).
File di questa versione
references/11.0 KB
- api-reference.md1.0 KB
scripts/12.1 KB
- analyst.py2.1 KB
- LICENSE340 B
- SKILL.md3.2 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 | 0701b45f | 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