TruffleHog

What's Changed

• [INS-355] Added Hashicorp vault token detector by @MuneebUllahKhan222 in https://github.com/trufflesecurity/trufflehog/pull/4819
• Tighten JiraToken v1 verification by @shahzadhaider1 in https://github.com/trufflesecurity/trufflehog/pull/5122
• [INT-718] Add TargetNotFoundError for targeted scan targets missing from the source by @bill-rich in https://github.com/trufflesecurity/trufflehog/pull/5123
• Fix GitLab project metadata cache and switch to LRU by @kashifkhan0771 in https://github.com/trufflesecurity/trufflehog/pull/4727
• Log analyze errors for Anthropic Analyzer by @kashifkhan0771 in https://github.com/trufflesecurity/trufflehog/pull/5120
• Add metrics for chunks and results by @mcastorina in https://github.com/trufflesecurity/trufflehog/pull/5128
• Update Cloudflare detectors for 2026+ prefixed credential formats (include upstream PR changes) by @kashifkhan0771 in https://github.com/trufflesecurity/trufflehog/pull/5111
• [INS-312] Duo API Secret Key Detector by @MuneebUllahKhan222 in https://github.com/trufflesecurity/trufflehog/pull/4771
• [Feature] Added SonarQube Cloud "Scoped Organization Token" Detector by @nabeelalam in https://github.com/trufflesecurity/trufflehog/pull/4739
• [INS-255] Updated datadog detector to set verificationError in case of a verification error by @MuneebUllahKhan222 in https://github.com/trufflesecurity/trufflehog/pull/4661
• Log analyze errors for Postgres analyzer by @kashifkhan0771 in https://github.com/trufflesecurity/trufflehog/pull/5131
• Log analyze errors for HuggingFace analyzer by @kashifkhan0771 in https://github.com/trufflesecurity/trufflehog/pull/5130
• Engine - Config.SourceManager doc by @amanfcp in https://github.com/trufflesecurity/trufflehog/pull/5002
• Update module github.com/go-git/go-git/v5 to v5.19.1 [SECURITY] by @renovate[bot] in https://github.com/trufflesecurity/trufflehog/pull/5034
• Retry git clone on transient network errors by @shahzadhaider1 in https://github.com/trufflesecurity/trufflehog/pull/5132
• Fix scan_all_installations Rejecting Org Member Personal Repos by @shahzadhaider1 in https://github.com/trufflesecurity/trufflehog/pull/5142
• updated detector to include underscore char by @mattbrady-1 in https://github.com/trufflesecurity/trufflehog/pull/5121
• [chore] Change job_id in metric to source_type by @mcastorina in https://github.com/trufflesecurity/trufflehog/pull/5149
• Posthog regex update by @mattbrady-1 in https://github.com/trufflesecurity/trufflehog/pull/5133
• fix(handlers): apk handler now doesnt check for apk extension since json-enumerator and other byte stream methods wouldnt have it by @johannestaas-trufflesec in https://github.com/trufflesecurity/trufflehog/pull/5151

New Contributors

• @mattbrady-1 made their first contribution in https://github.com/trufflesecurity/trufflehog/pull/5121

Full Changelog: https://github.com/trufflesecurity/trufflehog/compare/v3.95.9...v3.96.0

<p align="center">

<img alt="GoReleaser Logo" src="https://storage.googleapis.com/trufflehog-static-sources/pixel_pig.png" height="140" />

<h2 align="center">TruffleHog</h2>

<p align="center">Find leaked credentials.</p>

</p>

---

<div align="center">

Go Report Card

License

Total Detectors

</div>

---

:mag_right: _Now Scanning_

<div align="center">

<img src="assets/scanning_logos.svg">

...and more

To learn more about TruffleHog and its features and capabilities, visit our product page.

</div>

:globe_with_meridians: TruffleHog Enterprise

Are you interested in continuously monitoring Git, Jira, Slack, Confluence, Microsoft Teams, Sharepoint (and more) for credentials? We have an enterprise product that can help! Learn more at <https://trufflesecurity.com/trufflehog-enterprise>.

We take the revenue from the enterprise product to fund more awesome open source projects that the whole community can benefit from.

</div>

What is TruffleHog 🐽

TruffleHog is the most powerful secrets Discovery, Classification, Validation, and Analysis tool. In this context, secret refers to a credential a machine uses to authenticate itself to another machine. This includes API keys, database passwords, private encryption keys, and more.

Discovery 🔍

TruffleHog can look for secrets in many places including Git, chats, wikis, logs, API testing platforms, object stores, filesystems and more.

Classification 📁

TruffleHog classifies over 800 secret types, mapping them back to the specific identity they belong to. Is it an AWS secret? Stripe secret? Cloudflare secret? Postgres password? SSL Private key? Sometimes it's hard to tell looking at it, so TruffleHog classifies everything it finds.

Validation ✅

For every secret TruffleHog can classify, it can also log in to confirm if that secret is live or not. This step is critical to know if there’s an active present danger or not.

Analysis 🔬

For the 20 some of the most commonly leaked out credential types, instead of sending one request to check if the secret can log in, TruffleHog can send many requests to learn everything there is to know about the secret. Who created it? What resources can it access? What permissions does it have on those resources?

:loudspeaker: Join Our Community

Have questions? Feedback? Jump into Slack or Discord and hang out with us.

Join our Slack Community

Join the Secret Scanning Discord

:tv: Demo

GitHub scanning demo

docker run --rm -it -v "$PWD:/pwd" trufflesecurity/trufflehog:latest github --org=trufflesecurity

:floppy_disk: Installation

Several options are available for you:

MacOS users

brew install trufflehog

Docker:

_{<i>_Ensure Docker engine is running before executing the following commands:_</i>}

&nbsp;&nbsp;&nbsp;&nbsp;Unix

docker run --rm -it -v "$PWD:/pwd" trufflesecurity/trufflehog:latest github --repo https://github.com/trufflesecurity/test_keys

&nbsp;&nbsp;&nbsp;&nbsp;Windows Command Prompt

docker run --rm -it -v "%cd:/=\%:/pwd" trufflesecurity/trufflehog:latest github --repo https://github.com/trufflesecurity/test_keys

&nbsp;&nbsp;&nbsp;&nbsp;Windows PowerShell

docker run --rm -it -v "${PWD}:/pwd" trufflesecurity/trufflehog github --repo https://github.com/trufflesecurity/test_keys

&nbsp;&nbsp;&nbsp;&nbsp;M1 and M2 Mac

docker run --platform linux/arm64 --rm -it -v "$PWD:/pwd" trufflesecurity/trufflehog:latest github --repo https://github.com/trufflesecurity/test_keys

Binary releases

Download and unpack from https://github.com/trufflesecurity/trufflehog/releases

Compile from source

git clone https://github.com/trufflesecurity/trufflehog.git
cd trufflehog; go install

Using installation script

curl -sSfL https://raw.githubusercontent.com/trufflesecurity/trufflehog/main/scripts/install.sh | sh -s -- -b /usr/local/bin

Using installation script, verify checksum signature (requires cosign to be installed)

curl -sSfL https://raw.githubusercontent.com/trufflesecurity/trufflehog/main/scripts/install.sh | sh -s -- -v -b /usr/local/bin

Using installation script to install a specific version

curl -sSfL https://raw.githubusercontent.com/trufflesecurity/trufflehog/main/scripts/install.sh | sh -s -- -b /usr/local/bin <ReleaseTag like v3.56.0>

:closed_lock_with_key: Verifying the artifacts

Checksums are applied to all artifacts, and the resulting checksum file is signed using cosign.

You need the following tool to verify signature:

• Cosign

Verification steps are as follows:

1. Download the artifact files you want, and the following files from the releases page.

• trufflehog\_{version}\_checksums.txt
• trufflehog\_{version}\_checksums.txt.pem
• trufflehog\_{version}\_checksums.txt.sig

1. Verify the signature:

   cosign verify-blob <path to trufflehog_{version}_checksums.txt> \
   --certificate <path to trufflehog_{version}_checksums.txt.pem> \
   --signature <path to trufflehog_{version}_checksums.txt.sig> \
   --certificate-identity-regexp 'https://github\.com/trufflesecurity/trufflehog/\.github/workflows/.+' \
   --certificate-oidc-issuer "https://token.actions.githubusercontent.com"

1. Once the signature is confirmed as valid, you can proceed to validate that the SHA256 sums align with the downloaded artifact:

   sha256sum --ignore-missing -c trufflehog_{version}_checksums.txt

Replace {version} with the downloaded files version

Alternatively, if you are using the installation script, pass -v option to perform signature verification.

This requires Cosign binary to be installed prior to running the installation script.

:rocket: Quick Start

1: Scan a repo for only verified secrets

Command:

trufflehog git https://github.com/trufflesecurity/test_keys --results=verified

Expected output:

🐷🔑🐷  TruffleHog. Unearth your secrets. 🐷🔑🐷

Found verified result 🐷🔑
Detector Type: AWS
Decoder Type: PLAIN
Raw result: AKIAYVP4CIPPERUVIFXG
Line: 4
Commit: fbc14303ffbf8fb1c2c1914e8dda7d0121633aca
File: keys
Email: counter <counter@counters-MacBook-Air.local>
Repository: https://github.com/trufflesecurity/test_keys
Timestamp: 2022-06-16 10:17:40 -0700 PDT
...

2: Scan a GitHub Org for only verified secrets

trufflehog github --org=trufflesecurity --results=verified

3: Scan a GitHub Org excluding archived repositories

trufflehog github --org=trufflesecurity --exclude-archived

4: Scan a GitHub Repo for only verified secrets and get JSON output

Command:

trufflehog git https://github.com/trufflesecurity/test_keys --results=verified --json

Expected output:

{"SourceMetadata":{"Data":{"Git":{"commit":"fbc14303ffbf8fb1c2c1914e8dda7d0121633aca","file":"keys","email":"counter \u003ccounter@counters-MacBook-Air.local\u003e","repository":"https://github.com/trufflesecurity/test_keys","timestamp":"2022-06-16 10:17:40 -0700 PDT","line":4}}},"SourceID":0,"SourceType":16,"SourceName":"trufflehog - git","DetectorType":2,"DetectorName":"AWS","DecoderName":"PLAIN","Verified":true,"Raw":"AKIAYVP4CIPPERUVIFXG","Redacted":"AKIAYVP4CIPPERUVIFXG","ExtraData":{"account":"595918472158","arn":"arn:aws:iam::595918472158:user/canarytokens.com@@mirux23ppyky6hx3l6vclmhnj","user_id":"AIDAYVP4CIPPJ5M54LRCY"},"StructuredData":null}
...

5: Scan a GitHub Repo + its Issues and Pull Requests

trufflehog github --repo=https://github.com/trufflesecurity/test_keys --issue-comments --pr-comments

6: Scan an S3 bucket for high-confidence results (verified + unknown)

trufflehog s3 --bucket=<bucket name> --results=verified,unknown

7: Scan S3 buckets using IAM Roles

trufflehog s3 --role-arn=<iam role arn>

8: Scan a Github Repo using SSH authentication in Docker

docker run --rm -v "$HOME/.ssh:/root/.ssh:ro" trufflesecurity/trufflehog:latest git ssh://github.com/trufflesecurity/test_keys

9: Scan individual files or directories

trufflehog filesystem path/to/file1.txt path/to/file2.txt path/to/dir

10: Scan a local git repo

Clone the git repo. For example test keys repo.

git clone git@github.com:trufflesecurity/test_keys.git

Run trufflehog from the parent directory (outside the git repo).

trufflehog git file://test_keys --results=verified,unknown

To guard against malicious git configs in local scanning (see CVE-2025-41390), TruffleHog clones local git repositories to a temporary directory prior to scanning. This follows Git's security best practices. If you want to specify a custom path to clone the repository to (instead of tmp), you can use the --clone-path flag. If you'd like to skip the local cloning process and scan the repository directly (only do this for trusted repos), you can use the --trust-local-git-config flag.

11: Scan GCS buckets for only verified secrets

trufflehog gcs --project-id=<project-ID> --cloud-environment --results=verified

12: Scan a Docker image for only verified secrets

Use the --image flag multiple times to scan multiple images.

# to scan from a remote registry
trufflehog docker --image trufflesecurity/secrets --results=verified

# to scan from the local docker daemon
trufflehog docker --image docker://new_image:tag --results=verified

# to scan from an image saved as a tarball
trufflehog docker --image file://path_to_image.tar --results=verified

13: Scan in CI

Set the --since-commit flag to your default branch that people merge into (ex: "main"). Set the --branch flag to your PR's branch name (ex: "feature-1"). Depending on the CI/CD platform you use, this value can be pulled in dynamically (ex: CIRCLE_BRANCH in Circle CI and TRAVIS_PULL_REQUEST_BRANCH in Travis CI). If the repo is cloned and the target branch is already checked out during the CI/CD workflow, then --branch HEAD should be sufficient. The --fail flag will return an 183 error code if valid credentials are found.

trufflehog git file://. --since-commit main --branch feature-1 --results=verified,unknown --fail

14: Scan a Postman workspace

Use the --workspace-id, --collection-id, --environment flags multiple times to scan multiple targets.

trufflehog postman --token=<postman api token> --workspace-id=<workspace id>

15: Scan a Jenkins server

trufflehog jenkins --url https://jenkins.example.com --username admin --password admin

16: Scan an Elasticsearch server

Scan a Local Cluster

There are two ways to authenticate to a local cluster with TruffleHog: (1) username and password, (2) service token.

Connect to a local cluster with username and password

trufflehog elasticsearch --nodes 192.168.14.3 192.168.14.4 --username truffle --password hog

Connect to a local cluster with a service token

trufflehog elasticsearch --nodes 192.168.14.3 192.168.14.4 --service-token ‘AAEWVaWM...Rva2VuaSDZ’

Scan an Elastic Cloud Cluster

To scan a cluster on Elastic Cloud, you’ll need a Cloud ID and API key.

trufflehog elasticsearch \
  --cloud-id 'search-prod:dXMtY2Vx...YjM1ODNlOWFiZGRlNjI0NA==' \
  --api-key 'MlVtVjBZ...ZSYlduYnF1djh3NG5FQQ=='

17. Scan a GitHub Repository for Cross Fork Object References and Deleted Commits

The following command will enumerate deleted and hidden commits on a GitHub repository and then scan them for secrets. This is an alpha release feature.

trufflehog github-experimental --repo https://github.com/<USER>/<REPO>.git --object-discovery

In addition to the normal TruffleHog output, the --object-discovery flag creates two files in a new $HOME/.trufflehog directory: valid_hidden.txt and invalid.txt. These are used to track state during commit enumeration, as well as to provide users with a complete list of all hidden and deleted commits (valid_hidden.txt). If you'd like to automatically remove these files after scanning, please add the flag --delete-cached-data.

Note: Enumerating all valid commits on a repository using this method takes between 20 minutes and a few hours, depending on the size of your repository. We added a progress bar to keep you updated on how long the enumeration will take. The actual secret scanning runs extremely fast.

For more information on Cross Fork Object References, please read our blog post.

18. Scan Hugging Face

Scan a Hugging Face Model, Dataset, Space or Bucket

trufflehog huggingface \
    --model <model_id> \
    --dataset <dataset_id> \
    --space <space_id> \
    --bucket <bucket_id>

Scan all Models, Datasets, Spaces and Buckets belonging to a Hug