loading
Loading content
loading
Discovery
Hunt public GitHub code for leaked credential files.
overview
git-wild-hunt queries the GitHub code search API for files that match a secret-shaped --search expression. It pulls matching public files and writes hits for review, not live-host secret scanning.
Shape the hunt with path, filename, extension, and language qualifiers. A query like path:.aws/ filename:credentials or path:.kube filename:config chases one leak class. The config file sets run behavior and should point output at /hive/out/results.json.
Reach for it during a public-footprint exposure pass when you expect credential files in committed source. Pair with a JSON parse stage to separate live secrets from search noise before anyone acts.
use cases
Search for path and filename patterns like .aws/credentials or .azure access tokens to surface cloud secrets that developers pushed to public GitHub by mistake.
Sweep public GitHub for the kinds of files your engineers handle, then collect the hits into a results file so security can review what is exposed before an attacker finds it.
Target path:.kube filename:config and similar expressions to catch cluster configs, kubeconfigs, and service files that carry credentials in plaintext.
Write results as JSON, then parse and filter them downstream so the team works from a deduplicated list of real secrets instead of raw search noise.
reference
| Name | Type | Flag | Description |
|---|---|---|---|
| config | FILE | · | Config file path that controls the run; the repository ships a template, and the output variable should point at /hive/out/results.json. |
| search | STRING | --search | GitHub search query to execute, for example path:.aws/ filename:credentials or path:.kube filename:config. |
Showing key inputs. git-wild-hunt exposes 2 inputs in total.
example
# hunt public GitHub for AWS credential filesgit-wild-hunt --search 'path:.aws/ filename:credentials'api.example.comstaging.example.comci.example.comops.example.commail.example.comvpn.example.comgitlab.example.comcdn.example.comguidance
Use git-wild-hunt when the leak lives in public GitHub source, not on a running host. Drive it with a tight --search and a config that lands results as JSON. Pair with gh-scraper for broader GitHub collection, or gh-investigator when you need to pivot from a hit to the pushing account.
Broader GitHub repository and code collector. git-wild-hunt targets credential-shaped --search queries.
Hunts GitHub for a vulnerable pattern, not leaked secrets. Same source, different target.
Investigates GitHub accounts and activity. Pivot from a leaked file to the user or org that pushed it.
faq
related
Extract URLs and endpoints from Android APK files.
Web path scanner.
Crawl pages, harvest potential parameters, write a custom wordlist.
Recursive content discovery with smart defaults and rich response filters.
Maintained gau fork for passive archive URL collection.
Extract JavaScript file URLs from a page or URL list.
A config and search query drive git-wild-hunt, which hunts public GitHub for matching secrets and passes the results to a parser so triaged, leaked credentials land as output.
Facts on this page come from the live Trickest tool library.