ioc-batch
Bulk-enrich a list of IOCs through mlab.sh with quota management - takes a CSV, text file or pasted list of mixed indicators, enriches each with the right tool, and produces a machine-usable CSV plus a human summary. Use when the user provides a file or list of multiple indicators to check, enrich, or turn into a blocklist.
- License 许可
- MIT
- 最近更新
- 2026-10-22
- Stars
- ★ 1
- Forks
- 0
01 前言 Front Matter
- name
- ioc-batch
- description
- Bulk-enrich a list of IOCs through mlab.sh with quota management - takes a CSV, text file or pasted list of mixed indicators, enriches each with the right tool, and produces a machine-usable CSV plus a human summary. Use when the user provides a file or list of multiple indicators to check, enrich, or turn into a blocklist.
03 SKILL.md 正文
IOC Batch Enrichment
Before interpreting any tool result, read
${CLAUDE_PLUGIN_ROOT}/docs/tool-reference.md: verified output shapes and gotchas that override intuition.
Single indicators belong to ioc-triage; this skill is for lists. The difference is discipline: quota, dedupe, and machine-readable output.
Workflow
1. Parse and dedupe
Read the input (file or pasted). Extract candidate indicators, dedupe exactly, and drop obvious non-IOCs (RFC1918 addresses, example.com, the user's own domains if declared in .mlab/stack.md). Type ambiguous strings with detect_ioc - it catches defanged forms the eye misses - but type obvious IPs by shape locally: detect_ioc on an IP runs the full IP lookup and consumes IP quota. Refang (hxxp -> http, [.] -> .) before submitting.
2. Budget BEFORE scanning
Call get_scan_limits. Count what the batch will consume against the four pools (ip, domain, file, crypto): IP, domain and crypto lookups cost quota; hashes, URLs, emails, MACs and phones do not. Present the bill:
47 indicators: 12 IPs + 8 domains will use 20 of your 100 remaining daily scans. Proceed?
If the batch exceeds remaining quota, propose a split: quota-free types now, quota types up to the limit ordered by likely relevance, the rest listed as unprocessed. Quotas are shared org-wide per day - burning them all is a decision for the user, not for you.
3. Enrich
Route each indicator to its tool (same table as ioc-triage). Domains: batch start_domain_scan calls, then poll results. Do NOT auto-pivot to actors/CVEs per indicator in batch mode - collect the pivot-worthy leads (malware families, KEV CVEs) and pivot once at the end on the distinct set.
4. Deliver two outputs
A CSV file (this is the deliverable, write it to disk):
indicator,type,verdict,score,key_evidence,source_link
One row per indicator, including failures (verdict=error) and unprocessed ones (verdict=skipped_quota), so the CSV always reconciles with the input count.
A summary in the conversation:
## Batch: <N> indicators (<X> malicious, <Y> suspicious, <Z> clean/unknown, <E> errors)
### Confirmed bad - block these
<the short list>
### Needs a human
<suspicious/conflicting findings, one line why>
### Shared infrastructure
<same ASN / same registrar / same cert across indicators - the campaign signal>
Quota used: <n>, remaining: <m>.
Rules
- Every input indicator appears in the output CSV exactly once; reconciliation beats speed.
unknownnever becomescleanin the CSV.- On a mid-batch error or quota exhaustion, finish what can be finished and mark the rest; never silently truncate.
04 同仓库更多 Skills
threat-watch
Generate a threat landscape digest from mlab.sh - recent critical/KEV CVEs filtered to a declared technology stack, with actor attribution. Use when the user asks what is new in vulnerabilities, wants a daily/weekly threat brief, asks about recent CVEs for a product, or sets up a recurring watch on their stack.
supply-chain-audit
Full supply-chain audit of a project - postmortem detects malicious code, install hooks and risky dependencies locally, then mlab.sh enriches what it finds (hashes, endpoints, actors, CVEs). Use when the user asks to audit a project's dependencies or supply chain, check a repo for malicious packages, or vet a codebase before adoption or deployment.
smishing-campaign
Analyze a batch of reported SMS/text messages through mlab.sh - score each for smishing, cluster them into campaigns, and extract the shared infrastructure (URLs, callback numbers, sender patterns). Use when the user has multiple reported SMS from users/employees, or investigates an SMS phishing wave. For a single message, phishing-triage does the job.
script-triage
Statically analyze a suspicious shell script through mlab.sh - install.sh, cron payloads, CI steps, curl-pipe-sh one-liners. Flags dangerous constructs (download-piped-to-shell, base64 decoding, reverse shells, persistence, anti-forensics, destructive deletes), extracts every IOC and enriches them. Use when the user pastes shell code and asks if it is safe/malicious, or provides a .sh file to vet before running it.
sbom-export
Generate a CycloneDX SBOM locally with postmortem and push it through mlab.sh vulnerability scanning - for projects or container images where no single lockfile can be pasted. Use when the user asks for an SBOM, needs vuln scanning of a container image or a multi-ecosystem repo, or when sbom-audit lacks a usable lockfile.
sbom-audit
Audit a dependency lockfile or SBOM for known vulnerabilities via mlab.sh, prioritize findings by KEV status and EPSS, and attribute actively exploited CVEs to threat actors. Use when the user provides a lockfile (package-lock.json, yarn.lock, pnpm-lock.yaml, Cargo.lock, requirements.txt, poetry.lock, uv.lock, Pipfile.lock, go.sum, composer.lock, Gemfile.lock, pom.xml, gradle.lockfile, packages.lock.json, pubspec.lock, mix.lock) or a CycloneDX / SPDX SBOM, or asks to check dependencies for vulnerabilities.