ioc-extract

ioc-extract is a command for Claude Code from HermeticOrmus/LibreSecOps-Claude-Code. It costs 44 tokens per session (1,062 once invoked), scanned A, original, MIT.

A command that finds indicators of compromise—such as suspicious files, domains, IP addresses, and other traces—from malware reports, incident notes, and logs, then organizes them into structured records.

In plain words
What is it for?
Use it after malware analysis or during incident response to extract and categorize evidence from sandbox reports, network logs, forensic data, and threat intelligence reports.
Why use it?
It removes the manual work of searching messy security text and turning scattered findings into consistent threat intelligence or SIEM-ready data.

Command for Claude Code

Written for Claude Code: argument-hint in frontmatter.

Part of the malware-analysis plugin — 2 skills, 2 commands, 2 agents shipped together

Good fit Use it after malware analysis or during incident response to extract and categorize evidence from sandbox reports, network logs, forensic data, and threat intelligence reports.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/hermeticormus/libresecops-claude-code/ioc-extract
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Clone the repo
git clone --depth 1 https://github.com/HermeticOrmus/LibreSecOps-Claude-Code

Made for: Claude Code.

Or install malware-analysis, the plugin that ships this one along with the rest of its 2 skills, 2 commands, 2 agents.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for ioc-extract

README.md
[![agentmods](https://agentmods.dev/badge/commands/hermeticormus/libresecops-claude-code/ioc-extract/github.svg)](https://agentmods.dev/commands/hermeticormus/libresecops-claude-code/ioc-extract)
Your own site
<a href="https://agentmods.dev/commands/hermeticormus/libresecops-claude-code/ioc-extract"><img src="https://agentmods.dev/badge/commands/hermeticormus/libresecops-claude-code/ioc-extract/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for ioc-extract

Your own site · 80×15
<a href="https://agentmods.dev/commands/hermeticormus/libresecops-claude-code/ioc-extract"><img src="https://agentmods.dev/badge/commands/hermeticormus/libresecops-claude-code/ioc-extract.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 44 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,062 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00044 $0.01062
Opus 5.5 $0.00018 $0.00425
Sonnet 5.5 $0.00009 $0.00212
Haiku 4.5 $0.00004 $0.00106

Measured 12d ago against content hash fb701ef7132e, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

ioc-extract scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 12d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

plugins/malware-analysis/commands/ioc-extract.md · 118 lines

How it starts

The opening of the file, as written. The whole thing — 118 lines — stays where its author put it; the contents beside it link to each section on GitHub.

/ioc-extract

Extract, categorize, and format indicators of compromise from analysis notes, sandbox reports, or raw data into structured, actionable intelligence.

Trigger

Use after completing malware analysis (static or dynamic) or when processing threat intelligence reports, incident response notes, or any unstructured data that contains indicators of compromise. Also useful for converting informal analyst notes into structured IOC formats suitable for SIEM ingestion, threat intel platforms, or information sharing.

Input

Provide any of the following:

  • Analysis notes from static or dynamic malware analysis sessions
  • Sandbox reports (full text or key sections from ANY.RUN, Joe Sandbox, Cuckoo, etc.)
  • Network captures or Zeek/Suricata logs showing suspicious traffic
  • Incident response notes with observed artifacts
  • Threat intelligence reports containing IOCs mixed with narrative
  • Raw data (log entries, PCAP summaries, forensic artifacts)

The input can be messy and unstructured -- the command's purpose is to extract and organize.

Process

  1. Indicator extraction -- Scan the input for all indicator types:

    Network indicators:

    • IPv4 and IPv6 addresses (excluding RFC 1918 private ranges and known-good infrastructure unless flagged)
    • Domain names and subdomains (defang format accepted: hxxps://, [.]com)
    • Full URLs including paths and parameters
    • Email addresses (sender and recipient in phishing contexts)
    • JA3/JA3S TLS fingerprint hashes
    • JARM fingerprints
    • SSL certificate hashes and subject strings
    • User-Agent strings

    Host indicators:

    • File hashes (MD5, SHA-1, SHA-256) -- validate format and length
    • File names and paths (with OS context)
    • Registry key paths and values (Windows)
    • Mutex / named pipe names
    • Scheduled task names and configurations
    • Service names and descriptions
    • WMI event subscription details

    Behavioral indicators:

    • Process creation command lines
    • API call sequences that indicate specific techniques
    • MITRE ATT&CK technique IDs and descriptions

Read the full file on GitHub · 118 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 12d ago Changed · +5 lines · +44 tokens per session fb701ef7132e
  2. 1mo ago First seen · 113 lines · 0 tokens per session scan A 547bf1eb7b51

Subscribe to this mod's changes

ioc-extract is a command published in the GitHub repository HermeticOrmus/LibreSecOps-Claude-Code (4 stars, last pushed 9d ago), licensed MIT. It adds 44 tokens to every session and 1,062 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.