Ioc Extract
Pull indicators of compromise from a file or directory (URLs, IPs, domains, emails, md5/sha1/sha256 hashes, .onion, CVEs, BTC/ETH addresses, registry keys) — from text and from strings mined out of binaries. Every value is DEFANGED in output (hxxp://evil[.]com, 1[.]2[.]3[.]4) so a report can't ship a live IOC. Pure stdlib, read-only; never resolves or fetches anything.
Install
$ agentstack add skill-batteryshark-rekit-ioc-extract ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Links to your public security report.[](https://agentstack.voostack.com/security/report/skill-batteryshark-rekit-ioc-extract) Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
IOC Extractor
Pull indicators of compromise out of a file or directory — and defang them so the output is safe to drop into a report. Pure-stdlib, read-only.
When to use
Building a report, or triaging what a sample talks to: run it over source, configs, an extracted archive, or a decompiled tree. It also mines strings out of binaries, so it works on executables too.
What it finds
URLs, IPv4, domains, emails, file hashes (md5/sha1/sha256), .onion addresses, CVEs, crypto addresses (BTC/ETH), and Windows registry keys.
Everything is defanged in the output — hxxps://evil[.]com/x, 1[.]2[.]3[.]4, user[@]bad[.]com — so pasting the results can't create a live link or get a URL auto-fetched. Both the raw value and the defanged form are in the JSON.
Noise control: domains are filtered against a filename-extension blocklist (so index.js isn't a "domain"), IPs against octet + benign-address checks. It never resolves, connects to, or validates any indicator.
Usage
rekit run ioc-extract ./decompiled-src
rekit run ioc-extract ./sample.bin --format jsonPrerequisites
- python3 ≥ 3.8 — pure stdlib, nothing to vendor.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: batteryshark
- Source: batteryshark/rekit
- License: Apache-2.0
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.