Skip to content
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/enriching-iocs-with-threat-intel-sourcesMalware and ransomware analysis

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-sources

Writes to ⁦~/.notholy/skills⁩ after checking the signature and the SHA-256.

SignatureSigned, ed25519
nX2SZGDT4Y…WWHU6xDg==The CLI checks the SHA-256 and the signature before it writes a file.
Package0701b45f…f8c9142f
0701b45f781d…8532f8c9142f4 files · ⁦3.0 KB⁩
ScanMedium2 findings
  • Executable script shipped with the skillscripts/analyst.py
  • Links to outside domains
See the full scan
Sourcegithub.com/meltedinhex/analyst-ai-pack/tree/main/skills/enriching-iocs-with-threat-intel-sources@da7600a

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.

bash
python scripts/analyst.py plan iocs.json

Step 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.md for the lookup planner.
  • MITRE ATT&CK and passive-DNS enrichment concepts (linked in frontmatter).

Files in this version

Permissions

PermissionDeclaredFound by the scan
Reads filesNoNo
Writes filesNoNo
Runs shell commandsYesYes
Uses the networkYesYes
Uses connectorsNoNo
Drives a browserNoNo

Scan findings

Reviewed on Nov 13, 2026

  1. MediumFile · Executable script shipped with the skillscripts/analyst.py
  2. InfoLink · Links to outside domains

A clean scan lowers the risk but does not prove a package is safe. Read what you install.

VersionPublishedCommitSHA-256SignaturePermission change
v1.0.0Nov 13, 2026da7600a0701b45fSigned–

Ask anything your scope allows.

Create an account, add credits and ask the first question in the chat or the terminal.

  1. 1/3

    Create the account

    Individual or company. You can switch to a company later without losing balance or keys.

    IndividualCompany
  2. 2/3

    Add credits

    By card. Pay per token, no subscription.

    $5.00minimum deposit
  3. 3/3

    Ask

    In the chat, or install the CLI and run notholy login in your terminal.

    $ notholy login