IOC Lookup: $ARGUMENTS
Automatically detect the IOC type and run the appropriate enrichment chain.
Step 1: Identify IOC Type
Determine what type of indicator was provided:
- IPv4/IPv6 address → run IP enrichment
- Domain name → run domain enrichment
- URL → run URL enrichment
- MD5 (32 hex) / SHA1 (40 hex) / SHA256 (64 hex) → run file hash enrichment
- Email address → run email enrichment
If the type is ambiguous, ask for clarification.
IP Address Enrichment
Run all applicable checks:
Geolocation & ASN
- Country, city, ASN, ISP, organization
- Is it a datacenter/hosting/VPN/Tor exit node?
Reputation
- VirusTotal:
get_ip_report — detection count, community score
- Shodan:
ip_lookup — open ports, running services, banners, SSL certs, hostnames
- AbuseIPDB category if available
Threat Intelligence
- AlienVault OTX: pulse hits, threat actor associations
- Is this IP in any known C2 infrastructure databases?
- Recent malicious activity reported?
Passive DNS
- What domains has this IP hosted? (Shodan reverse DNS)
- How long has it been active?
- Any suspicious hosting patterns?
ATT&CK Context
If associated with known threat activity, map to ATT&CK:
- Infrastructure technique: T1583 (Acquire Infrastructure), T1584 (Compromise Infrastructure)
- C2 technique if applicable
Verdict: [Malicious / Suspicious / Unknown / Benign]
Confidence: [High / Medium / Low]
Recommended action: [Block / Monitor / No action]
Domain Enrichment
WHOIS
- Registrar, registration date, expiry, registrant (if not privacy-protected)
- Newly registered? (< 30 days = higher risk)
- Privacy-protected registration?
DNS Records
- A/AAAA: what IPs does it resolve to?
- MX: mail servers (useful for phishing assessment)
- NS: nameservers
- TXT: SPF, DKIM, DMARC (phishing infrastructure assessment)
Reputation
- VirusTotal:
get_domain_report — detection count, categories, SSL cert history
- Shodan:
dns_lookup — resolution and hosting info
Threat Intelligence
- OTX: threat actor associations, pulse hits
- Is this a typosquat/lookalike of a legitimate domain?
- DGA (Domain Generation Algorithm) characteristics?
- Sinkholed?
Certificate Transparency
- Historical SSL certs (org name, SANs, issuer)
- Does the cert cover unexpected domains? (shared hosting / malicious infra)
ATT&CK Context
- T1566.002 (Spearphishing Link) if phishing
- T1583.001 (Acquire Domains) for C2 infrastructure
- T1071.001 (Web Protocols) for C2 comms
Verdict: [Malicious / Suspicious / Unknown / Benign]
Confidence: [High / Medium / Low]
Recommended action: [Block / Monitor / No action]
URL Enrichment
Reputation
- VirusTotal:
get_url_report — scan results from 70+ engines, downloaded files, contacted domains
- Check URL shortener expansion if applicable
Content Analysis (if safe to access)
- What does the page serve? Phishing kit? Malware dropper? Legitimate?
- Does it redirect? To where?
Infrastructure
- What IP does the hostname resolve to? (run IP enrichment on result)
- Hosting provider?
Threat Intelligence
- Known phishing campaign?
- Exploit kit delivery URL?
- Malware C2 endpoint?
Verdict: [Malicious / Suspicious / Unknown / Benign]
Confidence: [High / Medium / Low]
Recommended action: [Block URL / Block domain / Monitor / No action]
File Hash Enrichment
Basic Info
- Hash format: MD5 / SHA1 / SHA256
- File type (magic bytes if known)
- File size
Reputation
- VirusTotal:
get_file_report — detection ratio (X/72 engines), community score, first/last seen
- Family name if detected
- Tags: trojan, ransomware, backdoor, dropper, etc.
Behavioral Analysis (from VT sandbox)
- Network connections: C2 IPs/domains
- Dropped files
- Registry modifications
- Process injection techniques
- Persistence mechanisms
Threat Intelligence
- Known malware family?
- APT group attribution?
- Campaign associations?
ATT&CK Mapping
Map behaviors to ATT&CK techniques. Common patterns:
- T1055 (Process Injection)
- T1059 (Command and Scripting Interpreter)
- T1071 (Application Layer Protocol — C2)
- T1082 (System Information Discovery)
- T1543 (Create or Modify System Process — Persistence)
If MCP YARA tool available: run against known signatures.
Verdict: [Malicious — Family name / Suspicious / Unknown / Benign]
Confidence: [High / Medium / Low]
Recommended action: [Quarantine / Investigate / No action]
Email Address Enrichment
Breach Data
- Has this email appeared in known breach data? (via public APIs)
- What services were breached?
Domain Assessment
- Run domain enrichment on the email domain
- Is this a free provider (gmail, proton) or corporate?
- Is the domain newly registered or suspicious?
Threat Intelligence
- Used in phishing campaigns?
- Social engineering activity?
- Spamhaus / reputation lists?
Verdict: [Malicious / Suspicious / Unknown / Benign]
Confidence: [High / Medium / Low]
Step 2: Consolidated Report
After all enrichment is complete, output a structured summary:
IOC: $ARGUMENTS
Type: [IP / Domain / URL / Hash / Email]
Verdict: [Malicious / Suspicious / Unknown / Benign]
Confidence: [High / Medium / Low]
Key Findings:
- [Most important finding]
- [Second finding]
- [Third finding]
Threat Context:
- Malware family / Actor: [If known]
- ATT&CK techniques: [T-IDs]
- Campaign: [If known]
Sources:
- VirusTotal: [X/Y detections]
- Shodan: [Key finding]
- OTX: [Pulse hits]
- Other: [Any additional sources]
Recommended Actions:
1. [Immediate action]
2. [Follow-up action]
3. [Detection/hunting recommendation]
Related IOCs to investigate:
- [Connected IPs, domains, hashes from the analysis]
Step 3: Detection Recommendations
Based on the findings, suggest at least one hunting/detection rule:
- SIEM query to find other systems that communicated with this IOC
- EDR query for process/network patterns
- DNS query pattern to detect similar domains (DGA, typosquats)
- YARA rule structure if this is a file hash
1---2name: ioc-lookup3description: Enriches an indicator of compromise (IP, domain, URL, file hash, or email). Pulls reputation data, threat intelligence, WHOIS, passive DNS, malware associations, and ATT&CK context. Use during incident response, threat hunting, or alert triage.4argument-hint: "[IP address | domain | URL | MD5/SHA1/SHA256 | email]"5disable-model-invocation: true6metadata:7 source: https://skillmd.com/skills/njones17/ioc-lookup8---910# IOC Lookup: $ARGUMENTS1112Automatically detect the IOC type and run the appropriate enrichment chain.1314## Step 1: Identify IOC Type1516Determine what type of indicator was provided:17- **IPv4/IPv6 address** → run IP enrichment18- **Domain name** → run domain enrichment19- **URL** → run URL enrichment20- **MD5 (32 hex) / SHA1 (40 hex) / SHA256 (64 hex)** → run file hash enrichment21- **Email address** → run email enrichment2223If the type is ambiguous, ask for clarification.2425---2627## IP Address Enrichment2829Run all applicable checks:3031### Geolocation & ASN32- Country, city, ASN, ISP, organization33- Is it a datacenter/hosting/VPN/Tor exit node?3435### Reputation36- VirusTotal: `get_ip_report` — detection count, community score37- Shodan: `ip_lookup` — open ports, running services, banners, SSL certs, hostnames38- AbuseIPDB category if available3940### Threat Intelligence41- AlienVault OTX: pulse hits, threat actor associations42- Is this IP in any known C2 infrastructure databases?43- Recent malicious activity reported?4445### Passive DNS46- What domains has this IP hosted? (Shodan reverse DNS)47- How long has it been active?48- Any suspicious hosting patterns?4950### ATT&CK Context51If associated with known threat activity, map to ATT&CK:52- Infrastructure technique: T1583 (Acquire Infrastructure), T1584 (Compromise Infrastructure)53- C2 technique if applicable5455**Verdict:** [Malicious / Suspicious / Unknown / Benign]56**Confidence:** [High / Medium / Low]57**Recommended action:** [Block / Monitor / No action]5859---6061## Domain Enrichment6263### WHOIS64- Registrar, registration date, expiry, registrant (if not privacy-protected)65- Newly registered? (< 30 days = higher risk)66- Privacy-protected registration?6768### DNS Records69- A/AAAA: what IPs does it resolve to?70- MX: mail servers (useful for phishing assessment)71- NS: nameservers72- TXT: SPF, DKIM, DMARC (phishing infrastructure assessment)7374### Reputation75- VirusTotal: `get_domain_report` — detection count, categories, SSL cert history76- Shodan: `dns_lookup` — resolution and hosting info7778### Threat Intelligence79- OTX: threat actor associations, pulse hits80- Is this a typosquat/lookalike of a legitimate domain?81- DGA (Domain Generation Algorithm) characteristics?82- Sinkholed?8384### Certificate Transparency85- Historical SSL certs (org name, SANs, issuer)86- Does the cert cover unexpected domains? (shared hosting / malicious infra)8788### ATT&CK Context89- T1566.002 (Spearphishing Link) if phishing90- T1583.001 (Acquire Domains) for C2 infrastructure91- T1071.001 (Web Protocols) for C2 comms9293**Verdict:** [Malicious / Suspicious / Unknown / Benign]94**Confidence:** [High / Medium / Low]95**Recommended action:** [Block / Monitor / No action]9697---9899## URL Enrichment100101### Reputation102- VirusTotal: `get_url_report` — scan results from 70+ engines, downloaded files, contacted domains103- Check URL shortener expansion if applicable104105### Content Analysis (if safe to access)106- What does the page serve? Phishing kit? Malware dropper? Legitimate?107- Does it redirect? To where?108109### Infrastructure110- What IP does the hostname resolve to? (run IP enrichment on result)111- Hosting provider?112113### Threat Intelligence114- Known phishing campaign?115- Exploit kit delivery URL?116- Malware C2 endpoint?117118**Verdict:** [Malicious / Suspicious / Unknown / Benign]119**Confidence:** [High / Medium / Low]120**Recommended action:** [Block URL / Block domain / Monitor / No action]121122---123124## File Hash Enrichment125126### Basic Info127- Hash format: MD5 / SHA1 / SHA256128- File type (magic bytes if known)129- File size130131### Reputation132- VirusTotal: `get_file_report` — detection ratio (X/72 engines), community score, first/last seen133- Family name if detected134- Tags: trojan, ransomware, backdoor, dropper, etc.135136### Behavioral Analysis (from VT sandbox)137- Network connections: C2 IPs/domains138- Dropped files139- Registry modifications140- Process injection techniques141- Persistence mechanisms142143### Threat Intelligence144- Known malware family?145- APT group attribution?146- Campaign associations?147148### ATT&CK Mapping149Map behaviors to ATT&CK techniques. Common patterns:150- T1055 (Process Injection)151- T1059 (Command and Scripting Interpreter)152- T1071 (Application Layer Protocol — C2)153- T1082 (System Information Discovery)154- T1543 (Create or Modify System Process — Persistence)155156If MCP YARA tool available: run against known signatures.157158**Verdict:** [Malicious — Family name / Suspicious / Unknown / Benign]159**Confidence:** [High / Medium / Low]160**Recommended action:** [Quarantine / Investigate / No action]161162---163164## Email Address Enrichment165166### Breach Data167- Has this email appeared in known breach data? (via public APIs)168- What services were breached?169170### Domain Assessment171- Run domain enrichment on the email domain172- Is this a free provider (gmail, proton) or corporate?173- Is the domain newly registered or suspicious?174175### Threat Intelligence176- Used in phishing campaigns?177- Social engineering activity?178- Spamhaus / reputation lists?179180**Verdict:** [Malicious / Suspicious / Unknown / Benign]181**Confidence:** [High / Medium / Low]182183---184185## Step 2: Consolidated Report186187After all enrichment is complete, output a structured summary:188189```190IOC: $ARGUMENTS191Type: [IP / Domain / URL / Hash / Email]192Verdict: [Malicious / Suspicious / Unknown / Benign]193Confidence: [High / Medium / Low]194195Key Findings:196- [Most important finding]197- [Second finding]198- [Third finding]199200Threat Context:201- Malware family / Actor: [If known]202- ATT&CK techniques: [T-IDs]203- Campaign: [If known]204205Sources:206- VirusTotal: [X/Y detections]207- Shodan: [Key finding]208- OTX: [Pulse hits]209- Other: [Any additional sources]210211Recommended Actions:2121. [Immediate action]2132. [Follow-up action]2143. [Detection/hunting recommendation]215216Related IOCs to investigate:217- [Connected IPs, domains, hashes from the analysis]218```219220## Step 3: Detection Recommendations221222Based on the findings, suggest at least one hunting/detection rule:223224- SIEM query to find other systems that communicated with this IOC225- EDR query for process/network patterns226- DNS query pattern to detect similar domains (DGA, typosquats)227- YARA rule structure if this is a file hash