| name | source-leak-hunt |
| description | Mass scan for exposed env files, backups, and git configs. |
| version | 1.1.0 |
| revision_date | "2026-07-25T00:00:00.000Z" |
| license | MIT |
| platforms | ["linux"] |
| compatibility | Requires curl, grep |
| tags | ["recon","source-leak","exposure","secrets","wordpress"] |
| category | recon |
| related_skills | ["wp-mass-recon","js-secrets-extraction","error-log-mining","phpinfo-to-rce","deep-invade"] |
Source Leak Hunt Skill
Mass scanning for exposed sensitive files (.env, .git/config, wp-config.php.bak, debug.log, backup.sql, phpinfo.php, Dockerfile, etc.) with content-based false positive filtering. Source leaks are the second most common finding (~7% of targets) after WordPress user enumeration.
When to Use
- After
skill_view(name='wp-mass-recon') confirms a target is alive.
- Broad scanning across a batch of domains.
- When probing for credential exposure that enables deeper access.
- Complementing
skill_view(name='js-secrets-extraction') for client-side secrets.
Prerequisites
terminal with curl.
- List of live URLs (output from httpx or wp-mass-recon Phase 1).
- Persistence: output directory at
$OUTDIR/leaks/.
How to Run
TARGET="https://example.com"
for path in .env .git/config wp-config.php.bak debug.log backup.sql info.php phpinfo.php \
.env.backup .env.local .env.production wp-config.php~ .git/HEAD .backup.sql \
docker-compose.yml Dockerfile .DS_Store robots.txt sitemap.xml; do
code=$(curl -sk -o /dev/null -w "%{http_code}" --max-time 5 --connect-timeout 5 "$TARGET/$path")
[[ "$code" == "200" ]] && echo "HTTP 200: $TARGET/$path"
sleep 0.2
done
Quick Reference
| Path | What It Exposes | Severity |
|---|
.env | DB creds, API keys, app secrets |