sk_test_/pk_test_ in production builds — hygiene with consequences
No real funds move on leaked test keys — but test customer data becomes readable. KeyDrift reports medium, not critical. Scan free.
This page exists partly to demonstrate calibration: a leaked test key is reported medium severity here, not maximum, because no real funds can move. Honest severity scales build trust that matters when critical findings arrive.
What test exposure actually risks.
What a Stripe test-mode key is
Test-mode keys operate against sandbox data: fake customers, test cards, staged subscriptions.
sk_test_FAKE00000000000000000000The prefix is the claim: scanners and attackers alike identify the format before they know anything else about it, which is why recognition starts at the first characters rather than the last.
What it grants
Bounded but non-zero:
- Reads of any PII entered into staging flows (often real emails/addresses from QA).
- Disruption of test suites/integrations via abuse.
How it ends up in a bundle
Three arrival routes cover nearly every case we see:
- Env misconfiguration deploying staging config to prod paths.
- Copy-paste from docs/examples using test keys verbatim.
Does it belong in a browser?
Never intended client-side either; publishable pk_test_ is the browser-safe variant within test mode.
Rotate it
Standard apikeys console flow; also audit which staging data was reachable.
Find it in seconds
Open DevTools on the deployed site and search the built assets for sk_test_. If the search hits, the credential shipped; if it does not, check the chunks loaded on authenticated or interactive views, not just the landing page — the calling code often sits behind a route.
Manual searching proves one page on one day. KeyDrift fetches the deployment the way a browser would, follows chunks named only in route manifests, reads streamed hydration payloads, and classifies what it finds — secret, or public-by-design — so an anon key never shows up dressed as an emergency.
Make sure it stays gone
One more thing worth knowing before you close the tab: fixing this once does not end the story. Agents imitate whatever pattern is already in the repo, templates carry their own defaults, and the next feature request can reintroduce the same shape of code. Continuous monitoring re-scans every deploy and alerts only on change — new, regressed, resolved — so the comeback attempt is a notification instead of a quarter-end surprise.
Why this failure class persists
Zoom out and the pattern is bigger than one repo. AI-assisted output has outgrown review capacity everywhere at once, which means thousands of teams are making the same reasonable-looking tradeoffs in the same week. Nobody using modern tooling is uniquely exposed. The failure mode documented above is the modal outcome of velocity without verification, not evidence of carelessness.
How KeyDrift reports this exact finding
Report anatomy matters during incidents, so it is worth reading once calmly: masked string (never the live value — it ceases to exist outside the detection engine), salted fingerprint (trackable within your workspace, useless to strangers), chunk path (your starting point for a "git log -S" hunt), disposition (secret versus public-by-design), confidence (matches below 0.5 never reach the page at all).
Manual check, step by step
The full manual drill, for readers who want zero dependence on any tool: open the deployed site in a private window; launch DevTools → Sources; use Search-all-files (Ctrl/Cmd+Shift+F) for sk_test_; then repeat for the other marker families — eyJ, sk_live_, sk-proj-, AKIA, postgres, BEGIN PRIVATE KEY. Decode anything JWT-shaped before reacting, and classify public-by-design formats as expected guests rather than intruders.
Close the loop with monitoring
If you take one operational step from this page, make it this: put the URL under continuous monitoring (free tier covers one project daily). The first scan tells you whether you have a problem today; the schedule tells you whether the problem comes back next month after someone re-adds the convenient line.
Common questions
So don’t panic?
Don’t skip fixing either — it signals process drift where configs cross environments silently.
Does KeyDrift exaggerate test findings elsewhere?
The opposite: documented sample/demo keys are rejected by name to avoid crying wolf.
Run a free scan at keydrift.dev/scan — paste a URL or the bundle source itself, no account. Findings arrive masked, with the exact chunk they live in.