hunting-from-a-threat-intel-report
Operationalizes a threat intelligence report into hunts: extracting IOCs and TTPs,
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/hunting-from-a-threat-intel-reportWrites to ~/.notholy/skills after checking the signature and the SHA-256.
SignatureSigned, ed25519
Packageef4b4bd9…202bfbb7
ef4b4bd9da41…8cd2202bfbb74 files · 3.3 KBScanMedium2 findings
- Executable script shipped with the skillscripts/analyst.py
- Links to outside domains
Sourcegithub.com/meltedinhex/analyst-ai-pack/tree/main/skills/hunting-from-a-threat-intel-report@da7600a
On this page
When to Use
- You received a CTI report (vendor writeup, ISAC bulletin, IR report) and must operationalize it.
- You want to convert narrative TTPs and IOC lists into concrete hunts against your telemetry.
- You need to prioritize which indicators are worth hunting given they age at different rates.
Do not use an IOC blocklist as the whole engagement — atomic indicators (hashes, IPs) are trivially changed; durable value comes from hunting the behaviors (TTPs).
Prerequisites
- The report and a way to extract its IOCs and behavioral claims.
- Knowledge of your telemetry coverage to judge which TTPs are huntable.
Workflow
Step 1: Extract IOCs and TTPs
Pull atomic indicators (hashes, IPs, domains, URLs) and the behavioral TTPs (the report's "how"). Defang/normalize indicators for safe handling.
python scripts/analyst.py extract report.txtStep 2: Map to ATT&CK and the Pyramid of Pain
Tag behaviors with techniques and rank indicators by the Pyramid of Pain — prioritize TTPs and tools over hashes/IPs because they cost the adversary more to change.
Step 3: Check telemetry feasibility
For each TTP, confirm you have the data source to hunt it; note gaps as detection-engineering work.
Step 4: Build concrete hunts
Translate the high-value TTPs into queries (Sysmon, DNS, proxy, EDR), and sweep atomic IOCs as a quick first pass for current presence.
Step 5: Execute, document, and feed back
Run the hunts, record findings/gaps/negatives, escalate hits to IR, and convert durable logic into detections (Sigma).
Validation
- Both atomic IOCs and behavioral TTPs are extracted, not just the indicator list.
- Hunts target the highest-pain indicators feasible with your telemetry.
- Each TTP maps to a real data source or is logged as a coverage gap.
Pitfalls
- Stopping at IOC sweeps; the adversary rotates them and you miss the campaign.
- Hunting TTPs you have no telemetry for, producing false confidence.
- Failing to defang indicators, risking accidental execution/clicks.
References
- See
references/api-reference.mdfor the IOC/TTP extractor. - MITRE ATT&CK and the Pyramid of Pain (linked in frontmatter).
Files in this version
references/11.0 KB
- api-reference.md1.0 KB
scripts/12.8 KB
- analyst.py2.8 KB
- LICENSE340 B
- SKILL.md3.1 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 | ef4b4bd9 | 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 DFIR and threat hunting
See the category- hunting-for-command-and-control-beaconingmukul975/hunting-for-command-and-control-beaconing5
- audit-context-buildingtrailofbits/audit-context-building4
- incident-response-forensicssecurityskills/incident-response-forensics3
- extracting-credentials-from-memory-dumpmukul975/extracting-credentials-from-memory-dump3
- analyzing-browser-forensics-with-hindsightmukul975/analyzing-browser-forensics-with-hindsight3
- forensics-ctfaeondave/forensics-ctf3
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