Skip to main content
skill CX Codex

collecting-open-source-intelligence — Claude Code skill

collecting-open-source-intelligence is a Claude Code skill that connects public data on threat actors, domains, and infrastructure for passive reconnaissance and CTI reports.

Apache-2.0 257 installs ★ 36,511 updated 2026-08-31

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add mukul975/Anthropic-Cybersecurity-Skills --skill collecting-open-source-intelligence -a claude-code
Open on GitHub

What collecting-open-source-intelligence does

This skill examines threat actor infrastructure, phishing campaigns, and an organization’s external exposure through public sources. It connects passive DNS, WHOIS, ASN, SSL certificate, and related records to surface domains, IP addresses, and other indicators.

The workflow uses Maltego for graph analysis, Shodan for device and service searches, OSINT Framework for choosing sources, and SpiderFoot for automated correlation. Some tasks require a Maltego license, a Shodan API key, or SpiderFoot; the documented workflow also uses curl, whois, jq, and python.

Active scanning requires explicit written authorization. Without that approval, collection must stay passive.

What it helps with

  • investigate infrastructure behind a phishing campaign
  • connect domains, IP addresses, and certificates
  • enrich a threat actor profile with WHOIS and ASN data
  • expand related domains through a Maltego graph
  • export SpiderFoot findings to JSON

Example prompts for the agent

  • Investigate evil-domain.com using passive DNS, WHOIS, and certificate transparency data.
  • Correlate Shodan results with passive DNS and map the related infrastructure cluster.
  • Run SpiderFoot against evil-domain.com with sfp_shodan,sfp_virustotal,sfp_passivetotal and write the output to result.json.

How to install collecting-open-source-intelligence

1Skills CLI (Vercel)

npx skills add mukul975/Anthropic-Cybersecurity-Skills --skill collecting-open-source-intelligence -a claude-code

2Manually: put the files in place

~/.claude/skills/collecting-open-source-intelligence/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/collecting-open-source-intelligence/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about collecting-open-source-intelligence

How do I install collecting-open-source-intelligence in Claude Code?

Run npx skills add mukul975/Anthropic-Cybersecurity-Skills --skill collecting-open-source-intelligence -a claude-code, then check ~/.claude/skills/collecting-open-source-intelligence/SKILL.md.

What does collecting-open-source-intelligence do?

It gathers public information about threat actors, malicious domains, and infrastructure, then connects the findings for CTI work and external attack-surface research.

What do Maltego and Shodan require?

Maltego requires a CE or commercial license, while Shodan requires an API key. SpiderFoot is available as HX or as an open-source version.

Source text

SKILL.md · Apache-2.0
---
name: collecting-open-source-intelligence
description: 'Collects and synthesizes open-source intelligence (OSINT) about threat
  actors, malicious infrastructure, and attack campaigns using publicly available
  data sources, passive reconnaissance tools, and dark web monitoring. Use when investigating
  external threat actor infrastructure, performing pre-engagement reconnaissance for
  authorized red team assessments, or enriching CTI reports with publicly available
  adversary context. Activates for requests involving Maltego, Shodan, OSINT framework,
  SpiderFoot, or infrastructure reconnaissance.

  '
domain: cybersecurity
subdomain: threat-intelligence
tags:
- OSINT
- Maltego
- Shodan
- Recon-ng
- SpiderFoot
- threat-intelligence
- ATT&CK-T1591
- NIST-CSF
version: 1.0.0
author: mahipal
license: Apache-2.0
nist_csf:
- ID.RA-01
- ID.RA-05
- DE.CM-01
- DE.AE-02
mitre_attack:
- T1593.001
- T1589.002
- T1596.002
- T1590
- T1596.001
---
# Collecting Open-Source Intelligence

## When to Use

Use this skill when:
- Investigating external infrastructure associated with a phishing campaign targeting your organization
- Enriching threat actor profiles with publicly observable indicators (WHOIS, ASN data, SSL certificates)
- Conducting authorized attack surface discovery to understand your organization's external exposure

**Do not use** this skill for active scanning against targets without explicit written authorization — OSINT collection must remain passive (no packets sent to target systems) unless scope permits active recon.

## Prerequisites

- Maltego CE or commercial license for graph-based link analysis
- Shodan API key (https://shodan.io) for internet-wide device/service discovery
- OSINT Framework familiarity (https://osintframework.com) for tool selection
- SpiderFoot HX or open-source SpiderFoot for automated OSINT correlation

## Workflow

### Step 1: Define Collection Requirements

Establish the intelligence requirement (IR) before collecting. Document:
- Target: threat actor group, malicious domain, IP range, or organization
- Priority Intelligence Requirements (PIRs): What specific questions need answering?
- Legal authority: Passive OSINT is legal; active probing requires authorization
- Data handling: TLP classification for collected intelligence

### Step 2: Passive DNS and WHOIS Investigation

```bash
# Passive DNS via SecurityTrails API
curl "https://api.securitytrails.com/v1/domain/evil-domain.com/dns/a" \
  -H "apikey: YOUR_KEY"

# WHOIS history via ARIN / RIPE
whois -h whois.arin.net evil-domain.com

# Certificate transparency logs (no API key required)
curl "https://crt.sh/?q=%.evil-domain.com&output=json" | jq '.[].name_value'
```

Certificate transparency logs reveal all subdomains for a target domain, often exposing staging, VPN, or internal infrastructure inadvertently made public.

### Step 3: Shodan Infrastructure Mapping

```python
import shodan

api = shodan.Shodan("YOUR_SHODAN_API_KEY")

# Search for specific C2 framework signatures (Cobalt Strike beacon)
results = api.search('product:"Cobalt Strike" port:443')
for r in results['matches']:
    print(r['ip_str'], r['port'], r['org'], r.get('ssl', {}).get('cert', {}).get('subject', ''))

# Find infrastructure associated with a known threat actor's ASN
results = api.search('asn:AS12345 http.title:"Redirector"')
```

Correlate Shodan results with passive DNS to build infrastructure clusters.

### Step 4: Maltego Graph Analysis

In Maltego, use these built-in transforms for threat actor infrastructure mapping:
1. Start with a known malicious domain (Entity: Domain)
2. Run "To IP Address [DNS]" → identifies hosting IPs
3. Run "To Shared Hosting" → identifies co-hosted domains (potentially same threat actor)
4. Run "To DNS Name [Reverse DNS]" → identifies PTR records
5. Run "To Whois" → identifies registrant email/organization
6. Pivot on registrant email → "To Domains [Registrant Email]" → expands to all domains registered with same email

Maltego Maltego Cyber threat intelligence transforms (VirusTotal, Shodan, PassiveTotal, URLScan) extend graph coverage.

### Step 5: Dark Web and Paste Site Monitoring

Use SpiderFoot HX or manual searches for:
- Paste sites (Pastebin, Ghostbin): search for leaked credentials, IOCs, malware configs
- Dark web forums: via Tor browser with appropriate operational security
- GitHub/GitLab: search for exposed credentials or organization-specific strings

```bash
# SpiderFoot CLI for automated OSINT
python sf.py -s evil-domain.com -m sfp_shodan,sfp_virustotal,sfp_passivetotal \
  -o TF -R result.json
```

## Key Concepts

| Term | Definition |
|------|-----------|
| **Passive OSINT** | Intelligence collection that does not send any packets to target systems — uses public databases, search engines, cached data |
| **PIR** | Priority Intelligence Requirement — specific question the intelligence collection must answer, preventing unfocused data gathering |
| **Certificate Transparency** | Public log of all SSL/TLS certificates issued by CAs, enabling discovery of subdomains via crt.sh |
| **Pivoting** | Using one data point (IP, email, registrant name) to discover related infrastructure or accounts |
| **ASN** | Autonomous System Number — block of IP addresses under a single routing policy; useful for clustering threat actor infrastructure |
| **Co-hosted Domains** | Multiple domains resolving to the same IP, potentially indicating shared attacker infrastructure |

## Tools & Systems

- **Maltego**: Graph-based link analysis platform with 50+ data source transforms for IP, domain, email, and social media analysis
- **Shodan**: Internet-wide scanner database with 1B+ indexed devices; supports banner, port, SSL certificate, and vulnerability searches
- **SpiderFoot**: Automated OSINT tool with 200+ modules covering DNS, WHOIS, dark web, breach data, and social media
- **Recon-ng**: Python-based OSINT framework with modular design for domain, email, and social media reconnaissance
- **crt.sh**: Free certificate transparency search engine for subdomain and certificate discovery
- **OSINT Framework (osintframework.com)**: Curated directory of OSINT tools organized by intelligence category

## Common Pitfalls

- **Leaving digital footprints**: Visiting a threat actor's website or Shodan-queried IP can alert the adversary. Use Tor or VPN with a dedicated OSINT VM.
- **Confirmation bias in graph analysis**: Maltego graphs can create false connections. Verify each pivot independently before treating as confirmed.
- **Outdated data**: WHOIS privacy services and bulletproof hosting rotate frequently. Always check data timestamps — 6-month-old passive DNS may no longer be valid.
- **Attribution overconfidence**: Infrastructure overlap does not guarantee same threat actor. False flag operations deliberately share indicators across groups.
- **Legal boundaries**: Some OSINT tools perform active scans (port scanning, banner grabbing). Confirm tool behavior before use against external targets without authorization.

© mahipal · Apache-2.0 · mukul975/Anthropic-Cybersecurity-Skills

Similar skills

All skills for Security →

From the same set152

The whole set →
analyzing-ransomware-payment-wallets The analyzing-ransomware-payment-wallets skill follows cryptocurrency payments after ransomware incidents, linking wallets, transactions, mixers, and exchange deposits for forensic analysis. CX Codex +1 262installs testing-for-xml-injection-vulnerabilities testing-for-xml-injection-vulnerabilities — a skill that walks an agent through XML injection testing: XXE, blind XXE, SSRF and XPath. Useful when the target parses XML somewhere in the request path. CX Codex +1 261installs exploiting-http-request-smuggling exploiting-http-request-smuggling — a skill that detects and exploits HTTP request smuggling caused by discrepancies in how front-end and back-end servers parse request boundaries. CX Codex +1 260installs performing-api-rate-limiting-bypass performing-api-rate-limiting-bypass — a skill for Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI and OpenCode tests API protection against rate-limit circumvention. CX Codex +1 259installs exploiting-insecure-deserialization exploiting-insecure-deserialization helps detect and exploit insecure deserialization bugs in Java, PHP, Python, and .NET applications during authorized penetration testing. CX Codex +1 256installs exploiting-oauth-misconfiguration exploiting-oauth-misconfiguration is a Claude Code skill for finding and exploiting OAuth 2.0 and OpenID Connect flaws in security assessments of apps with social login or SSO. CX Codex +1 256installs analyzing-threat-landscape-with-misp analyzing-threat-landscape-with-misp — a skill that queries MISP (Malware Information Sharing Platform) to surface event statistics, IOC type breakdowns, threat actor galaxy clusters, and tag trends. CX Codex +1 256installs implementing-api-key-security-controls implementing-api-key-security-controls generates prefixed API keys with 256-bit entropy, enforces SHA-256 hashing, scopes IP permissions, and manages zero-downtime rotation for backend services. CX Codex +1 255installs

Project sponsors

Companies that keep this analytics open