Skip to content
Back to skills

Recon Osint

ASecurity

Passive OSINT to expand attack surface without touching the target: dorks, code/secret leaks, Shodan/Censys, cloud assets, employees. Load at recon start, on "OSINT", "google/github dorks", "shodan", or gathering intel on an org. Signals: org name, root domain, "find leaks/exposed".

  • 20 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added September 22, 2026
ai-agentsgotestinggitapidatabase

Works with

  • api

Security analysis

A100/100

Scanned September 22, 2026

npx -y skills add NoorQureshi/SploitAgent --skill recon-osint --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Recon Osint?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Recon Osint
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/noorqureshi-recon-osint/badge)](https://www.skillsdirectory.com/skills/noorqureshi-recon-osint)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: recon-osint
description: >
  Passive OSINT to expand attack surface without touching the target: dorks, code/secret leaks,
  Shodan/Censys, cloud assets, employees. Load at recon start, on "OSINT", "google/github dorks",
  "shodan", or gathering intel on an org. Signals: org name, root domain, "find leaks/exposed".
domain: recon
type: technique
stability: learning
modes: [bugbounty]
severity: info
mitre: [T1593, T1596, T1589]
tools: [github-search, shodan, censys, google-dorks, trufflehog]
schema_version: 1
---

# Passive OSINT

## When it applies
Early recon, and anytime you want surface/intel without sending traffic to the target — safest,
often highest-signal (leaked keys, forgotten hosts, exposed services).

## Why it works
Organizations leak everywhere but their own site: search-engine indexes, public code, internet
scan databases, cloud metadata, and employee footprints. Aggregating these finds assets and
secrets the target doesn't know are exposed.

## Method
1. **Search dorks**: Google (`site: inurl: filetype: intitle:` for panels, configs, docs) and
   GitHub dorks (`org:target "api_key"`, `"target.com" password`) for code/secret leaks.
2. **Code leaks**: `trufflehog github --org=<org>`, gist/pastebin search — validate live keys (in scope).
3. **Internet scan DBs**: Shodan/Censys/FOFA by org/cert/favicon-hash to find exposed services,
   forgotten hosts, and origin IPs behind CDNs.
4. **Cloud & DNS assets**: CT logs, reverse-DNS, ASN ranges, bucket name guessing (→ `cloud-s3-exposure`).
5. **People/tech**: employees (LinkedIn) for username formats/phishing scope (if allowed), and
   job posts/stack sites for the tech stack.

## Gotchas
- Confirm everything you find is in program scope before *active* testing — OSINT surfaces out-of-scope acquisitions too.
- Report leaked secrets by location, validate minimally, never exfiltrate.
- Origin-IP discovery via Shodan/cert often bypasses the WAF later (→ `payloads-waf-bypass`).

## Verify success
New in-scope assets, exposed services, or validated leaked secrets — feeding active recon and hunting.

## References
Google Hacking DB; GitHub dorks lists; Shodan/Censys docs; trufflehog.

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…