enriching-iocs-with-threat-intel-sources
Enriches indicators with context from threat-intel sources: planning lookups against
v1.0.03 instalações+3 em 7 dias24 EstrelasApache-2.0sincronizado há 10 horas
Instalar
Ainda não tem a CLI da NotHoly? Instale primeiro.
$ curl -fsSL https://notholy.com/install.sh | sh$ notholy skills install meltedinhex/enriching-iocs-with-threat-intel-sourcesGrava em ~/.notholy/skills depois de conferir a assinatura e o SHA-256.
AssinaturaAssinado, ed25519
Pacote0701b45f…f8c9142f
0701b45f781d…8532f8c9142f4 arquivos · 3.0 KBVarreduraMédio2 achados
- Script executável junto com a skillscripts/analyst.py
- Links para domínios externos
Fontegithub.com/meltedinhex/analyst-ai-pack/tree/main/skills/enriching-iocs-with-threat-intel-sources@da7600a
Este item ainda não foi escrito no seu idioma, então aparece em English.
Nesta página
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).
Arquivos desta versão
references/11.0 KB
- api-reference.md1.0 KB
scripts/12.1 KB
- analyst.py2.1 KB
- LICENSE340 B
- SKILL.md3.2 KB
Permissões
| Permissão | Declarada | Encontrada na varredura |
|---|---|---|
| Lê arquivos | Não | Não |
| Grava arquivos | Não | Não |
| Roda comandos no shell | Sim | Sim |
| Usa a rede | Sim | Sim |
| Usa conectores | Não | Não |
| Controla um navegador | Não | Não |
Achados da varredura
Revisado em 13 de nov. de 2026
- MédiaArquivo · Script executável junto com a skillscripts/analyst.py
- InfoLink · Links para domínios externos
Uma varredura limpa reduz o risco, mas não prova que o pacote é seguro. Leia o que você instala.
| Versão | Publicada em | Commit | SHA-256 | Assinatura | Mudança de permissão |
|---|---|---|---|---|---|
| v1.0.0 | 13 de nov. de 2026 | da7600a | 0701b45f | Assinada | – |
Mais de meltedinhex
Tudo deste publicador- 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
Mais em Análise de malware e ransomware
Ver a 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
Pergunte tudo o que o seu escopo permite.
Crie a conta, adicione créditos e faça a primeira pergunta no chat ou no terminal.
- 1/3
Crie a conta
Individual ou empresa. Dá para virar empresa depois sem perder saldo nem chaves.
Pessoa físicaEmpresa - 2/3
Adicione créditos
No cartão. Você paga por token, sem assinatura.
$5.00recarga mínima - 3/3
Pergunte
No chat, ou instale o CLI e rode notholy login no terminal.
$ notholy login