What problem does it solve?
Manually crafting effective Google dorks to locate exposed sensitive data like credentials, configuration files, and secrets is time-consuming and often yields low-quality results, especially during the critical passive reconnaissance phase of security assessments.
Core Features & Use Cases
- Validated High-Precision Dorks: 100+ real-world tested queries for exposed files, service-specific secrets (AWS, Firebase, Supabase, etc.), and configuration leaks confirmed against 100+ real targets.
- GitHub Code Search Patterns: Pre-built API queries to find leaked credentials in public GitHub repositories, with filters to reduce false positives from example code.
- Use Case: For example, during the initial passive recon phase of a penetration test, use this skill to quickly identify exposed .env files, API keys, and private keys for a target domain without triggering active scanning alerts.
Quick Start
Use the google-dorks-catalog skill to run the validated exposed config dorks for your target domain to identify any publicly leaked sensitive files and credentials.