A secrets scanning tool that discovers, classifies, validates, and analyzes leaked credentials across multiple sources.
TruffleHog is an open-source security tool that scans for leaked credentials across various sources like Git repositories, cloud storage, and collaboration platforms. It detects secrets such as API keys, database passwords, and private encryption keys, then verifies them against live APIs to confirm their validity. The tool helps developers and security teams prevent data breaches by identifying exposed credentials before they can be exploited.
Security engineers, DevOps teams, and developers who need to proactively scan their codebases, infrastructure, and collaboration tools for accidentally committed or stored secrets. It's particularly valuable for organizations implementing DevSecOps practices.
Developers choose TruffleHog for its extensive detection capabilities, active verification that eliminates false positives, and support for a wide range of sources including Git, cloud platforms, and CI/CD systems. Its ability to analyze credential permissions provides deeper security insights than simple pattern matching.
Find, verify, and analyze leaked credentials
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
TruffleHog classifies over 800 secret types and scans diverse sources including Git, S3, Docker, and chat platforms, as shown in the scanning logos and feature list.
It validates credentials by testing against live APIs to confirm if they are active, reducing false positives, which is emphasized in the validation and FAQ sections.
The tool integrates easily into pipelines with GitHub Actions, pre-commit hooks, and Docker examples, including a dedicated section on scanning in CI.
For common credential types, it performs in-depth analysis to determine permissions and resource access, providing actionable security insights beyond mere detection.
Setting up scans for multiple sources requires YAML configuration files and understanding of each source's options, which can be overwhelming for new users.
Unauthenticated scans of platforms like GitHub face strict rate limits, necessitating personal access tokens for efficiency, as admitted in the FAQ.
The custom regex detector is labeled as alpha and subject to change, limiting reliability for organizations needing tailored detection rules.