threatcaddy
Read and write data in a live ThreatCaddy investigation session via Chrome DevTools Protocol
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
メニュー
Read and write data in a live ThreatCaddy investigation session via Chrome DevTools Protocol
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | threatcaddy |
| description | Read and write data in a live ThreatCaddy investigation session via Chrome DevTools Protocol |
Interact with a live ThreatCaddy investigation session running in Chrome. Create notes, IOCs, timeline events, tasks, and more — directly from your AI coding agent.
--remote-debugging-port=9222 (recommended, no popups)
/Applications/Google\ Chrome.app/Contents/MacOS/Google\ Chrome --remote-debugging-port=9222chrome://inspect/#remote-debugging → toggle on (shows allow popup each time)All commands use scripts/tc.mjs. The first command spawns a background daemon that holds the Chrome CDP session open. Chrome's "Allow debugging" popup fires once; all subsequent commands reuse the session silently. The daemon auto-exits after 20 minutes idle.
scripts/tc.mjs status
scripts/tc.mjs investigations
scripts/tc.mjs folder <investigation_id>
scripts/tc.mjs exec <tool_name> '<json_input>'
scripts/tc.mjs stop
{"query": "malware"} — Search notes by keyword{"query": "apt29"} — Search across all entity types{"id": "..."} or {"title": "..."} — Get full note content{"id": "..."} or {"title": "..."} — Get full task details{"id": "..."} or {"value": "10.0.0.1"} — Get full IOC details{"id": "..."} or {"title": "..."} — Get full event details{"status": "todo"} — List tasks, optional status filter{"type": "ipv4"} — List IOCs, optional type filter{"eventType": "initial-access"} — List events{} — Get entity counts and metadata{"title": "Finding", "content": "# Details"}{"id": "...", "appendContent": "New paragraph"}{"title": "Review logs", "priority": "high", "status": "todo"}{"id": "...", "status": "done"}{"type": "ipv4", "value": "10.0.0.1", "confidence": "high", "analystNotes": "C2 server"}{"id": "...", "confidence": "confirmed", "attribution": "APT29"}{"iocs": [{"type": "ipv4", "value": "10.0.0.1"}, {"type": "domain", "value": "evil.com"}]}{"title": "Phishing email", "timestamp": "2025-06-15T14:00:00Z", "eventType": "initial-access"}{"id": "...", "actor": "APT29"}{"links": [{"sourceType": "note", "sourceId": "...", "targetType": "task", "targetId": "..."}]}{"executiveSummary": "...", "findings": "..."}{"text": "Found IP 10.0.0.1 and domain evil.com"} — Extract IOCs from text{} — Analyze entity relationship graph{} — List all investigations{"name": "APT29"} — Detailed investigation summary{"query": "cobalt strike"} — Search all investigations{"investigationName": "APT29", "entityType": "note", "data": {"title": "...", "content": "..."}}{"investigationIds": ["id1", "id2"]} — Find shared IOCs and TTPsipv4, ipv6, domain, url, email, md5, sha1, sha256, cve, mitre-attack, yara-rule, sigma-rule, file-path
initial-access, execution, persistence, privilege-escalation, defense-evasion, credential-access, discovery, lateral-movement, collection, exfiltration, command-and-control, impact, detection, containment, eradication, recovery, communication, evidence, other
# Extract IOCs from a threat report
scripts/tc.mjs exec extract_iocs '{"text": "The actor used 185.220.101.1 to deliver payload.exe (SHA256: abc123...) via phishing from updates.evil.com"}'
# Bulk create the IOCs
scripts/tc.mjs exec bulk_create_iocs '{"iocs": [{"type":"ipv4","value":"185.220.101.1","confidence":"high","analystNotes":"C2 server"},{"type":"domain","value":"updates.evil.com","confidence":"high","analystNotes":"Phishing infrastructure"}]}'
# Create timeline events
scripts/tc.mjs exec create_timeline_event '{"title":"Phishing email delivered","timestamp":"2025-06-15T09:00:00Z","eventType":"initial-access","source":"Email gateway"}'
# Create follow-up tasks
scripts/tc.mjs exec create_task '{"title":"Block C2 IP at firewall","priority":"high","status":"todo"}'
# Create a note with analysis findings
scripts/tc.mjs exec create_note '{"title":"APT29 Infrastructure Analysis","content":"# Infrastructure Mapping\n\nThe following C2 infrastructure was identified..."}'
# Search across all investigations for related activity
scripts/tc.mjs exec search_across_investigations '{"query":"185.220.101"}'