ASSET LEAK DETECTION
Sensitive Files & Information Exposure Scout
Identify exposed .env secrets, git repositories, backup dumps, and leaked credentials.
Overview & Threat Landscape
Developers and DevOps teams inadvertently leave backup archives (`.zip`, `.sql`), `.git` folder metadata, and `.env` credentials in public web roots, giving attackers instant access to databases and cloud APIs.
Why Public Leaks are Fatal
01
Complete Database Compromise
Exposed `.env` files contain live database passwords, Stripe keys, AWS tokens, and SMTP credentials.
02
Source Code Exfiltration
Public `.git` directories allow automated scrapers to reconstruct your entire intellectual property and commit history.
03
Regulatory Penalties (GDPR/LGPD)
Exposing personal data through unattended backup files triggers severe statutory fines and liability.
Web Server Blocking Rule
Block all hidden dotfiles and backup extensions directly in your web server or Cloudflare WAF:
location ~ /\.(env|git|svn|htaccess) {
deny all;
return 404;
}
location ~* \.(bak|config|sql|tar|zip|gz)$ {
deny all;
return 404;
}