A tool for security researchers, penetration testers, and bug bounty hunters to identify potentially sensitive or exposed data within public GitHub repositories. This script leverages GitHub dorking techniques to help you find misconfigurations, exposed secrets, and vulnerable code that could pose a security risk.
Warning: This tool is intended for ethical hacking and security research only. Always ensure you have explicit permission before testing any systems, and respect the terms of service for the platforms you are interacting with.
- Installation: How to Install
- Usage: How to Use the Script
- Ethical Considerations: What You Need to Know
- License: MIT License
- 🚀 Quick Start
- 💻 Features
- 🔍 Use Cases
- 🛠 Installation
- 💡 Usage
- 📄 Input File Format
- 🔧 How It Works
- ⚖️ Ethical Considerations
- 📜 License
- 💬 Disclaimer
- Generate GitHub Search Queries: The script allows you to create search URLs based on a company name and a set of dorking keywords (e.g., "password", "secret", "private", etc.).
- Automated Search URL Generation: For each keyword, the script generates a GitHub search URL that can quickly locate repositories with potential security risks.
- Exclusion of False Positives: Automatically filters out irrelevant results (e.g., "test", "example") to refine your search and focus on more valuable targets.
- Command-Line Interface (CLI): Simple and flexible for integrating into penetration testing workflows or using in scripts for automation.
- Reconnaissance for Penetration Testing: Quickly identify sensitive information exposed on GitHub related to a specific target company or technology.
- Bug Bounty Hunting: Find exposed credentials, API keys, and other vulnerabilities in public repositories as part of a responsible bug bounty program.
- Security Research: Explore GitHub for potential security issues and public leaks, helping improve the overall security posture of organizations.
- Search for publicly exposed API keys, database credentials, or other sensitive data.
- Investigate repositories related to specific companies or technologies to identify potential security flaws.
- Locate configuration files that may have been accidentally uploaded and are vulnerable to exploitation.
- Python 3.x
- A text file containing dorking keywords (e.g.,
github_dorking_keywords.txt).
-
Clone the repository:
git clone https://github.com/sh1vam-03/gitman.git cd gitman -
No additional dependencies are required, as the script uses only standard Python libraries.
The script accepts the company related keyword and an optional path to a custom file containing dorking keywords. You can use it like this:
python gitman.py -k Google,TeslaThis will generate search URLs using the company name Google and Tesla with default github_dorking_keywords.txt file.
python gitman.py -k Googlepython gitman.py -k TeslaIf you have a custom list of dorking keywords (such as api_key, password, etc.), you can specify the file like this:
python gitman.py -k Google,Tesla -f custom_github_dorking_keywords.txtFor each keyword in the file, the script generates a URL similar to:
Generated GitHub Search URLs:
1 https://github.com/search?q=Google+"api_key"+NOT+test+NOT+example
2 https://github.com/search?q=Google+"api_key_secret"+NOT+test+NOT+example
3 https://github.com/search?q=Google+"api_key_sid"+NOT+test+NOT+example
1 https://github.com/search?q=Tesla+"api.googlemaps+AIza"+NOT+test+NOT+example
2 https://github.com/search?q=Tesla+"apidocs"+NOT+test+NOT+example
3 https://github.com/search?q=Tesla+"apikey"+NOT+test+NOT+example
...
These URLs direct you to GitHub search results that contain the target company name and the dorking keyword, excluding irrelevant entries like "test" or "example".
The input file should be a plain text file with one keyword per line. Empty lines or lines containing only whitespace will be ignored.
Example (github_dorking_keywords.txt):
"API key"
"password"
"secret"
"confidential"
"access token"
"private key"
- The script constructs GitHub search queries by appending the provided company related keywords and each keyword from the dorking file.
- It then generates search URLs like:
https://github.com/search?q=Google+API+key+NOT+test+NOT+example - The results filter out repositories related to "test" and "example" to help you focus on finding actual, potentially sensitive data.
Important: This tool is designed for ethical hacking purposes only. Before using it, ensure you have proper authorization to scan or interact with the target systems. Unauthorized scanning or data access could be illegal and violate GitHub's Terms of Service.
- Penetration Testing: Always conduct penetration testing only with explicit written permission from the target organization.
- Bug Bounty: If you’re using this tool for a bug bounty, ensure you're abiding by the program’s rules and guidelines.
- Legal Use: Never use this tool for malicious purposes or to exploit vulnerabilities without permission.
This script is not intended for malicious activities. The creators of this script are not responsible for any misuse of the tool. By using this script, you agree to take full responsibility for your actions and ensure they comply with local laws and ethical standards.
This project is licensed under the MIT License - see the LICENSE file for details.
- Customization: You can modify the
load_dorking_keywordsfunction to load keywords from any other source (like a database or an API). - Security Considerations: This script is intended to help identify exposed data. Always act responsibly and ensure that you do not inadvertently expose any data that could be sensitive or private.