ShadowDork is a next-generation command-line tool designed for Bug Bounty Hunters, Pentesters, and Security Researchers.
Unlike traditional dorking tools that aggressively query Google and get blocked by CAPTCHAs instantly, ShadowDork utilizes a Hybrid Search Architecture. It leverages DuckDuckGo's search infrastructure as a proxy to filter and verify active dorks without directly triggering Google's bot detection systems.
It transforms the tedious process of Google Hacking into a streamlined, automated, and safe workflow.
- Anti-Ban Architecture (Stealth Mode): Uses DuckDuckGo as a "Oracle" to verify if a dork returns results before you ever open Google. This minimizes interaction with Google servers, reducing the risk of IP bans and CAPTCHAs by 99%.
- Smart Verification Engine: The
-x(check) flag doesn't just ping the URL. It performs Client-Side Validation to ensure the target domain matches and eliminates false positives caused by search engine fuzziness. - Modular Data Structure: No more massive, unmanageable JSON files. Dorks are split into categorized files (
git.json,sqli.json,exposed_services.json), making it easy to maintain and contribute. - Precision Targeting: Includes a "Grep" feature (
-g) to run specific payloads (e.g.,-g 1-5,10) instead of scanning the entire category. - Preview Mode: Inspect payloads with IDs before running them using the
-Pflag. - Rich CLI Interface: Beautiful, readable, and interactive terminal output powered by the
richlibrary.
- Python 3.8 or higher
- pip (Python Package Manager)
-
Clone the Repository
git clone https://github.com/ayb-blc/ShadowDork.git cd ShadowDork -
Run the Installer
chmod +x install.sh ./install.sh
This script will set up a virtual environment, install requirements, and create a
./shadowdorkshortcut.
ShadowDork is designed to be intuitive.
Generate search links for a specific category and target.
./shadowdork -t uber.com -c git -oVerify which dorks actually return results before opening them in the browser.
./shadowdork -t uber.com -c files_sensitive -x -o -b firefox./shadowdork -c login -PThen, run only the selected IDs (e.g., ID 1, 2, and 5):
./shadowdork -t uber.com -c login -g 1,2,5 -x -o -b brave./shadowdork -l| Argument | Long Flag | Description |
|---|---|---|
-t |
--target |
Target domain (e.g., example.com). |
-c |
--category |
Dork category (e.g., git, sqli, logs). |
-x |
--check |
Live Check Mode. Verifies results via DDG to prevent empty tabs. |
-o |
--open |
Automatically opens valid links in your default browser. |
-g |
--grep |
Select specific Dork IDs to run (e.g., 1-5 or 1,3,9). |
-P |
--preview |
Lists payloads in a category with IDs without running them. |
-l |
--list |
Lists all available categories in the database. |
-e |
--engine |
Search engine logic (Default: ddg). |
-b |
--browser |
Specify browser (chrome, firefox, brave, default). |
ShadowDork uses a modular JSON system located in the data/ directory. Each file represents a category.
data/
├── git.json # Git exposure dorks
├── sqli.json # SQL Injection patterns
├── files_sensitive.json # .env, .conf, .log files
├── cloud_storage.json # AWS S3, Azure Blob leaks
└── ...
Want to add new dorks? Simply create a new .json file in the data/ folder (e.g., wordpress.json). The tool will automatically detect and load it on the next run. No code changes required!
ShadowDork is created for educational purposes and authorized security testing (Pentesting/Bug Bounty) only.
Do not use this tool on domains you do not own or do not have explicit permission to audit.
The developer assumes no responsibility for any misuse or damage caused by this program.
Google Dorking is a passive reconnaissance technique, but automated queries may violate some Terms of Service. Use responsibly.
Contributions are welcome! If you have a new list of dorks or a feature idea:
- Fork the repository.
- Create a new branch (git checkout -b feature/AmazingFeature).
- Commit your changes.
- Push to the branch.
- Open a Pull Request.
Made with ❤️ by Ayberk Balcı