What Is Exposed API Keys?
Exposed secrets are one of the most common — and most damaging — vulnerabilities in modern web apps. An API key, database URL, or service token that ships to the browser, gets committed to a public repo, or sits in a readable config file can be extracted in seconds. With it, an attacker can run up your cloud bill, read your database, send mail as you, or pivot deeper. Minification and obfuscation do not protect secrets; only keeping them server-side does.
How Exposed API Keys Shows Up
Secrets in the client bundle
Keys compiled into frontend JavaScript (e.g. NEXT_PUBLIC_/build-time vars) are visible to anyone who opens DevTools.
Committed to version control
.env files, master.key, and hardcoded tokens pushed to git remain in history even after deletion, and public repos are scraped automatically.
Service keys that bypass everything
A leaked Supabase service_role key or cloud root credential grants full access regardless of your app-level rules.
Third-party token abuse
Leaked Stripe, OpenAI, Twilio, or webhook tokens let attackers spend your money or impersonate your services.
How the Sable Scan Detects It
Live bundle scanning
We scan your served JavaScript and API responses against 100+ secret patterns and flag the exact key and location.
Exposed config detection
We test for publicly reachable .env, config, and credential files.
Validated, not guessed
Findings are confirmed by an agent so you get real leaks with remediation, not regex false positives.
Check Your App for Exposed API Keys
Create a free account and let the agents test your app. Every finding is validated with a proof-of-concept and remediation. 150 founder credits, no credit card.
Get 150 Free Credits