Hunt organization secrets across GitHub

Aug 13, 2026 · 1 min read

Beyond the org’s own repos, current and former employees leak credentials in personal projects. Search broadly by domain and internal names, then scan history.

bash

# GitHub code search dorks
# "target.com" password  |  org:Target AKIA  |  filename:.env DB_PASSWORD
trufflehog github --org=Target --only-verified

Scan a specific interesting repo including all history.

bash

gitleaks detect --source ./repo --log-opts="--all"

Pro note: pivot on unique internal strings (project codenames, internal hostnames, Slack workspace names) which are less noisy than generic dorks. Verified secrets are worth triaging first; rotate-detection tools reduce false positives from long-dead keys.