enriching-iocs-with-threat-intel-sources
Enriches indicators with context from threat-intel sources: planning lookups against
v1.0.03 installs+3 in 7 days24 StarsApache-2.0synced 10 hours ago
Install
No NotHoly CLI yet? Install it first.
$ curl -fsSL https://notholy.com/install.sh | sh$ notholy skills install meltedinhex/enriching-iocs-with-threat-intel-sourcesWrites to ~/.notholy/skills after checking the signature and the SHA-256.
SignatureSigned, ed25519
Package0701b45f…f8c9142f
0701b45f781d…8532f8c9142f4 files · 3.0 KBScanMedium2 findings
- Executable script shipped with the skillscripts/analyst.py
- Links to outside domains
Sourcegithub.com/meltedinhex/analyst-ai-pack/tree/main/skills/enriching-iocs-with-threat-intel-sources@da7600a
On this page
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).
Files in this version
references/11.0 KB
- api-reference.md1.0 KB
scripts/12.1 KB
- analyst.py2.1 KB
- LICENSE340 B
- SKILL.md3.2 KB
Permissions
| Permission | Declared | Found by the scan |
|---|---|---|
| Reads files | No | No |
| Writes files | No | No |
| Runs shell commands | Yes | Yes |
| Uses the network | Yes | Yes |
| Uses connectors | No | No |
| Drives a browser | No | No |
Scan findings
Reviewed on Nov 13, 2026
- MediumFile · Executable script shipped with the skillscripts/analyst.py
- InfoLink · Links to outside domains
A clean scan lowers the risk but does not prove a package is safe. Read what you install.
| Version | Published | Commit | SHA-256 | Signature | Permission change |
|---|---|---|---|---|---|
| v1.0.0 | Nov 13, 2026 | da7600a | 0701b45f | Signed | – |
More from meltedinhex
All from this publisher- 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
More in Malware and ransomware analysis
See the category- 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
Ask anything your scope allows.
Create an account, add credits and ask the first question in the chat or the terminal.
- 1/3
Create the account
Individual or company. You can switch to a company later without losing balance or keys.
IndividualCompany - 2/3
Add credits
By card. Pay per token, no subscription.
$5.00minimum deposit - 3/3
Ask
In the chat, or install the CLI and run notholy login in your terminal.
$ notholy login