Shodan Dorking

When to Use

• During the passive reconnaissance phase of a penetration test or bounty program to identify an organization's public-facing attack surface without directly interacting with their servers.
• To hunt for specific vulnerabilities, exposed Industrial Control Systems (ICS), or easily exploitable services (e.g., open RDP, unauthenticated databases) on a wide scale.

Prerequisites

• Target IP range, domain, or organization scope defined
• Reconnaissance tools installed (Shodan CLI, Censys, Nmap)
• API keys for passive reconnaissance services (Shodan, VirusTotal, SecurityTrails)
• Understanding of passive vs active reconnaissance and legal boundaries

Workflow

Phase 1: Basic Filters & Organization Searching

# shodan search org:"Target Company Inc"

# shodan search ssl.cert.subject.cn:"target.com"

Phase 2: Hunting Vulnerable Services

# "MongoDB Server Information" port:27017 -authentication

# port:9200 "status": 200 "cluster_name"

Phase 3: Hardware & IoT Discovery

# superbly "default password" port:80 "admin:admin"

# neutrally port:502

Phase 4: Exploiting CVE Specific Dorks

# properly "Server: Microsoft-IIS/10.0" "Set-Cookie: MS-Exchange"

# "X-Forwarded-For" "Apache-Coyote"

Decision Point 🔀

flowchart TD
    A[Construct Dork ] --> B{Results Found ]}
    B -->|Yes| C[Verify ]
    B -->|No| D[Broaden Scope ]
    C --> E[Document Asset ]

🔵 Blue Team Detection & Defense

• Hide Server Banners: Network Firewalls (VPCs): Monitor Shodan IP Ranges: Key Concepts

  Concept	Description

Output Format

Shodan Dorking — Assessment Report
============================================================
Target: [Target identifier]
Assessor: [Operator name]
Date: [Assessment date]
Scope: [Authorized scope]
MITRE ATT&CK: [Relevant technique IDs]

Findings Summary:
  [Finding 1]: [Severity] — [Brief description]
  [Finding 2]: [Severity] — [Brief description]

Detailed Results:
  Phase 1: [Phase name]
    - Result: [Outcome]
    - Evidence: [Screenshot/log reference]
    - Impact: [Business impact assessment]

  Phase 2: [Phase name]
    - Result: [Outcome]
    - Evidence: [Screenshot/log reference]
    - Impact: [Business impact assessment]

Risk Rating: [Critical/High/Medium/Low/Informational]
Recommendations:
  1. [Immediate remediation step]
  2. [Long-term hardening measure]
  3. [Monitoring/detection improvement]

📚 Shared Resources

For cross-cutting methodology applicable to all vulnerability classes, see:

• _shared/references/elite-chaining-strategy.md — Exploit chaining methodology and high-payout chain patterns
• _shared/references/elite-report-writing.md — HackerOne-optimized report writing, CWE quick reference
• _shared/references/real-world-bounties.md — Verified disclosed bounties by vulnerability class

References

• Shodan Help: Search Query Syntax
• OSINT Framework: OSINT Tools