collecting-indicators-of-compromise
Systematically collects, categorizes, and distributes indicators of compromise (IOCs) during and after security incidents to enable detection, blocking, and…
Skill by mukul975
Chalk Labs
Need help deploying collecting-indicators-of-compromise?
Chalk Labs sets up agents like this inside real teams: connected to your tools, tested on your data, with a human in the loop where it matters.
Install
Works with Claude Code, Claude apps, Codex, Cursor, Gemini CLI, GitHub Copilot, VS Code, OpenCode, Goose, Windsurf. Read the repository before you give any tool access to your data.
npx agentmarket install skill/mukul975-collecting-indicators-of-compromise
Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.
Get the weekly diff
The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.
About
Use cases: security, productivity
Reviews
Write a reviewNo reviews yet. Installed it? Reviews come from verified installers only. How reviews work
Permissions
What this skill can do and what it asks for, from its SKILL.md and code. Checked Nov 1, 2026.
- Tools
- No tools found
- Secrets
- None asked for
- Install scripts
- None found
- Runs as
- Python package
Network hosts it talks to 4
api.abuseipdb.com· found in codecodeload.github.com· found in install commandmb-api.abuse.ch· found in codevirustotal.com· found in code
Files it touches
~/.claude/skills/collecting-indicators-of-compromise
What's inside
- Skill name
collecting-indicators-of-compromise- Description
- Systematically collects, categorizes, and distributes indicators of compromise (IOCs) during and after security incidents to enable detection, blocking, and threat intelligence sharing. Covers network, host, email, and behavioral indicators using STIX/TAXII formats and threat intelligence platforms. Activates for requests involving IOC collection, indicator extraction, threat indicator sharing, compromise indicators, STIX export, or IOC enrichment.
- License
- Apache-2.0
- Instructions
- 239 lines in SKILL.md · view on GitHub
Before installing
- Ships executable scripts
Agent Skills spec issues
- body: contains an absolute path from the author's machine
Files (4)
- LICENSE
- SKILL.md
- api-reference.md · references/
- agent.py · scripts/
SKILL.md (first lines)
# Collecting Indicators of Compromise ## When to Use - During active incident response to identify and block adversary infrastructure - Post-incident to document all observed adversary artifacts for future detection - When sharing threat intelligence with ISACs, sector partners, or law enforcement - When building detection rules in SIEM, EDR, or network security tools - When enriching IOCs with threat intelligence context for risk scoring **Do not use** for behavioral TTP analysis without accompanying technical indicators; use MITRE ATT&CK mapping for behavioral characterization. ## Prerequisites - Access to incident evidence sources: SIEM logs, EDR telemetry, memory dumps, disk images, network captures - Threat intelligence platform (MISP, OpenCTI, ThreatConnect) for IOC management and sharing - IOC enrichment tools: VirusTotal, OTX (AlienVault Open Threat Exchange), Shodan, DomainTools - STIX 2.1 knowledge for structured IOC representation - Sharing agreements with relevant ISACs (FS-ISAC, H-ISAC, IT-ISAC) or sector partners ## Workflow ### Step 1: Identify IOC Categories Collect indicators across all categories from incident evidence: **Network Indicators:** - IP addresses (C2 servers, staging servers, exfiltration destinations) - Domain names (C2 domains, phishing domains, DGA domains) - URLs (malware download, C2 check-in, exfiltration endpoints) - JA3/JA3S hashes (TLS client/server fingerprints) - User-Agent strings (custom or unusual HTTP headers) - DNS query patterns (tunneling signatures, DGA patterns) **Host Indicators:** - File hashes (MD5, SHA-1, SHA-256 of malware, tools, scripts) - File paths (known malware installation directories) - Registry keys (persistence mechanisms, configuration storage) - Scheduled tasks and service names (persistence) - Mutex/event names (malware instance synchronization) - Named pipes (C2 communication channels, e.g., Cobalt Strike) **Email Indicators:** - Sender addresses and domains (spoofed or attacker-controlled) - Subject lines and body content patterns - Attachment names and hashes - Embedded URLs - Email header anomalies (SPF/DKIM/DMARC failures) ### Step 2: Extract IOCs from Evidence Sources Systematically extract indicators from each evidence source: **From SIEM/Log Analysis:** ``` # Extract unique destination IPs from firewall logs index=firewall action=blocked | stats count by dest_ip | where count > 100 # Extract domains from DNS query logs index=dns query=*evil* OR query=*c2* | stats count by query ``` **From Memory Forensics:** ```bash # Extract network connections vol -f memory.raw windows.netscan | grep ESTABLISHED # Extract strings from suspicious process memory vol -f memory.raw windows.memmap --pid 3847 --dump strings -n 8 pid.3847.dmp | grep -E "(http|https)://" ``` **From Malware Analysis:** ``` Sandbox Report IOC Extraction: - Dropped files: 3 (hashes extracted) - DNS queries: update.evil[.]com, cdn.malware[.]net - HTTP connections: POST to https://185.220.101[.]42/gate.php - Registry modified: HKCU\Software\Microsoft\Windows\CurrentVersion\Run\svcupdate - Mutex created: Global\MTX_0x1234ABCD - Named pipe: \\.\pipe\MSSE-1234-server ``` ### Step 3: Enrich IOCs with Context Add threat intelligence context to each indicator: ``` IOC Enrichment Report: ━━━━━━━━━━━━━━━━━━━━━ IP: 185.220.101.42 VirusTotal: 12/89 vendors flag as malicious Shodan: Open ports: 443, 8443, 80 Geolocation: Netherlands, AS208476 First Seen: 2025-10-01 Threat Intel: Associated with Qakbot C2 infrastructure Confidence: High TLP: AMBER Domain: update.evil[.]com Registration: 2025-10-28 (recently registered) Registrar: Namecheap WHOIS Privacy: Yes VirusTotal: 8/89 vendors flag as malicious DNS History: Resolved to 185.220.101.42, 91.215.85.17 Confidence: High TLP: AMBER ``` ### Step 4: Score and Prioritize IOCs Assign confidence and risk scores to each indicator: | Score | Confidence Level | Criteria | |-------|-----------------|----------| | 90-100 | Confirmed Malicious | Multiple TI sources confirm, observed in active attack |
From mukul975/Anthropic-Cybersecurity-Skills, Apache-2.0.
Signals
- Stars
- 34,941
- Forks
- 4,256
- Open issues
- 24
- Last commit (this folder)
- Jun 1, 2026 (5 months ago)
- Last release
- Jun 22, 2026 (5 months ago)
From GitHub (fetched Oct 24, 2026).
Details
- License
- Apache-2.0
- First seen
- Oct 24, 2026
- Last checked
- Oct 24, 2026
- Source
- GitHubgithub-graphql
Done for you
Rather not set it up yourself?
Chalk Labs scopes, builds and runs agents for your team: the task audit, the eval harness, the integrations and the weekly ops report. Fixed scope, priced before we start.
See how we build AI agents →Read the case studies
Chalk Labs is a two-founder AI and growth studio. We build AI agents, CRMs and MVPs for Web3 and AI companies, and have shipped 50+ product and token launches.
- launches shipped
- 50+
- launches shipped
- media placements
- 500+
- media placements
- founders on every account
- 2
- founders on every account
Press we've placed: Forbes · CoinDesk · Decrypt · Cointelegraph · The Block
Rahil Jain, Co-founder, Chalk Labs. Ex-Goldman Sachs engineer. You talk to the person who builds it.
Get collecting-indicators-of-compromise running in your business
Tell us what you want to automate. A founder replies within one working day with a plan, not a pitch deck.
Cite this page
collecting-indicators-of-compromise skill. Agent Mart. https://agentmart.dev/skills/mukul975-collecting-indicators-of-compromise (last updated 2026-10-24)