collecting-open-source-intelligence

mukul975/Anthropic-Cybersecurity-Skills · updated May 25, 2026

MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.

$npx skills install mukul975/Anthropic-Cybersecurity-Skills/collecting-open-source-intelligence
0 commentsdiscussion
summary

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.

skill.md
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

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

# 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

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
# 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

TermDefinition
Passive OSINTIntelligence collection that does not send any packets to target systems — uses public databases, search engines, cached data
PIRPriority Intelligence Requirement — specific question the intelligence collection must answer, preventing unfocused data gathering
Certificate TransparencyPublic log of all SSL/TLS certificates issued by CAs, enabling discovery of subdomains via crt.sh
PivotingUsing one data point (IP, email, registrant name) to discover related infrastructure or accounts
ASNAutonomous System Number — block of IP addresses under a single routing policy; useful for clustering threat actor infrastructure
Co-hosted DomainsMultiple 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.
how to use collecting-open-source-intelligence

How to use collecting-open-source-intelligence on Cursor

AI-first code editor with Composer

1

Prerequisites

Before installing skills in Cursor, ensure your development environment meets these requirements:

  • Cursor installed and configured on your development machine
  • Node.js version 16.0+ with npm package manager (verify with node --version)
  • Active project directory or workspace where you want to add collecting-open-source-intelligence
2

Execute installation command

Execute the skills CLI command in your project's root directory to begin installation:

$npx skills install mukul975/Anthropic-Cybersecurity-Skills/collecting-open-source-intelligence

The skills CLI fetches collecting-open-source-intelligence from GitHub repository mukul975/Anthropic-Cybersecurity-Skills and configures it for Cursor.

3

Select Cursor when prompted

The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:

◆ Which agents do you want to install to?
│ ── Universal (.agents/skills) ── always included ────
│ • Amp
│ • Antigravity
│ • Cline
│ • Codex
│ ●Cursor(selected)
│ • Cursor
│ • Windsurf
4

Verify installation

Confirm successful installation by checking the skill directory location:

.cursor/skills/collecting-open-source-intelligence

Reload or restart Cursor to activate collecting-open-source-intelligence. Access the skill through slash commands (e.g., /collecting-open-source-intelligence) or your agent's skill management interface.

Security & Verification Notice

We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.

Skills execute code in your development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.

List & Monetize Your Skill

Submit your Claude Code skill and start earning

GET_STARTED →

Use Cases

Task Automation & Efficiency

Automate repetitive workflows and reduce manual effort

Example

Generate reports, summarize documents, draft communications

Save 3-5 hours per week on routine tasks

Knowledge Enhancement

Learn new skills, understand complex topics, get expert guidance

Example

Explain concepts, provide examples, suggest learning resources

Accelerate learning and skill development by 2x

Quality Improvement

Enhance output quality through reviews, suggestions, and refinements

Example

Review drafts, suggest improvements, catch errors

Improve work quality by 30-40% with less effort

Implementation Guide

Prerequisites

  • Claude Desktop or compatible AI client with skill support
  • Clear understanding of task or problem to solve
  • Willingness to iterate and refine outputs

Time Estimate

15-45 minutes depending on use case complexity

Installation Steps

  1. 1.Install skill using provided installation command
  2. 2.Test with simple use case relevant to your work
  3. 3.Evaluate output quality and relevance
  4. 4.Iterate on prompts to improve results
  5. 5.Integrate into regular workflow if valuable

Common Pitfalls

  • Expecting perfect results without iteration
  • Not providing enough context in prompts
  • Using skill for tasks outside its intended scope
  • Accepting outputs without review and validation

Best Practices

✓ Do

  • +Start with clear, specific prompts
  • +Provide relevant context and constraints
  • +Review and refine all outputs before using
  • +Iterate to improve output quality
  • +Document successful prompt patterns

✗ Don't

  • Don't use without understanding skill limitations
  • Don't skip validation of outputs
  • Don't share sensitive information in prompts
  • Don't expect skill to replace human judgment

💡 Pro Tips

  • Be specific about desired format and style
  • Ask for multiple options to choose from
  • Request explanations to understand reasoning
  • Combine AI efficiency with human expertise

When to Use This

✓ Use When

Use when skill capabilities match your task, clear ROI on time saved, and you can validate outputs. Best for repetitive tasks, learning, and quality improvement.

✗ Avoid When

Avoid when task requires deep expertise you can't validate, involves sensitive decisions, or when learning process is more valuable than speed of completion.

Learning Path

  1. 1Familiarize yourself with skill capabilities and limitations
  2. 2Start with low-risk, non-critical tasks
  3. 3Progress to more complex and valuable use cases
  4. 4Build expertise through regular use and experimentation

Discussion

Product Hunt–style comments (not star reviews)
  • No comments yet — start the thread.
general reviews

Ratings

4.568 reviews
  • Kwame Huang· Dec 28, 2024

    Keeps context tight: collecting-open-source-intelligence is the kind of skill you can hand to a new teammate without a long onboarding doc.

  • Shikha Mishra· Dec 24, 2024

    collecting-open-source-intelligence fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.

  • Kwame Sanchez· Dec 24, 2024

    collecting-open-source-intelligence fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.

  • Chinedu Diallo· Dec 8, 2024

    Registry listing for collecting-open-source-intelligence matched our evaluation — installs cleanly and behaves as described in the markdown.

  • Chinedu Huang· Nov 27, 2024

    collecting-open-source-intelligence fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.

  • Mei Taylor· Nov 19, 2024

    collecting-open-source-intelligence has been reliable in day-to-day use. Documentation quality is above average for community skills.

  • Rahul Santra· Nov 15, 2024

    Registry listing for collecting-open-source-intelligence matched our evaluation — installs cleanly and behaves as described in the markdown.

  • Kwame Okafor· Nov 15, 2024

    Registry listing for collecting-open-source-intelligence matched our evaluation — installs cleanly and behaves as described in the markdown.

  • Charlotte Patel· Nov 3, 2024

    Useful defaults in collecting-open-source-intelligence — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.

  • Layla Mehta· Oct 22, 2024

    I recommend collecting-open-source-intelligence for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.

showing 1-10 of 68

1 / 7