Replit security scanner
Replit builds and hosts full-stack apps, and its Agent will happily wire up databases and third-party services for you. That speed is where keys get pasted into the wrong place and databases get left open. This page explains what to check and scans your live app now.
Scan your Replit app
What it means
A value shaped like a private key or password is in code your site serves, where anyone can read it. If it still works, anyone who copies it can act as you: run up bills, read your data, or send email in your name. xlogs did not test it.
Why AI tools cause it
AI coding tools often paste an API key straight into a file to make something work, instead of hiding it in a private environment variable. It runs fine, so nothing warns you.
How xlogs checks it
xlogs scans your live JavaScript against 18 key formats covering Stripe (live, test and webhook secrets), OpenAI, Anthropic, AWS, Google, GitHub, Slack, private key blocks, and Supabase server keys (service_role and sb_secret_).
What to check first on a Replit app
An exposed secret key is the first thing to check on a Replit app, because pasting a key into a file is the quickest way to make an integration work. If that file is part of the frontend, the key ships to every visitor. Then check for open databases (when the app uses Supabase or Postgres without access rules) and missing security headers.
You cannot see these while using the app. The scan below checks the deployed app the way an outsider would.
The top Replit security issues to check
- An API key or service key exposed in the client bundle
- A database table that returns rows to anonymous requests
- Missing security headers (CSP, HSTS, X-Frame-Options)
- Private files like .env served from the live site
How to fix it
The goal: The exposed key has been replaced and revoked at the provider, because removing it from the code does not stop it working, and the new value is stored only in a server-side secret or environment variable, never in code or the client bundle.
- Contain and rotate the exposed key first, because removing it from the code does not stop it working: if you suspect it is being misused, revoke it at the provider now; otherwise create a replacement, put it in the app's server-side secret settings, confirm the app works with it, and then revoke the exposed key promptly
- Remove the literal value from the code and any client-side bundle (the affected spot), so the key is read only from a server-only environment variable
- Make sure the .env file is in .gitignore
- Clear the old value from deployed builds and caches, and from the repository's history where you can; once the key is revoked, a copy left there no longer works
In my app (the spot the scan shows): a credential-shaped value is publicly served. Please make this true: The exposed key has been replaced and revoked at the provider, because removing it from the code does not stop it working, and the new value is stored only in a server-side secret or environment variable, never in code or the client bundle. Steps: Contain and rotate the exposed key first, because removing it from the code does not stop it working: if you suspect it is being misused, revoke it at the provider now; otherwise create a replacement, put it in the app's server-side secret settings, confirm the app works with it, and then revoke the exposed key promptly; Remove the literal value from the code and any client-side bundle (the spot the scan shows), so the key is read only from a server-only environment variable; Make sure the .env file is in .gitignore; Clear the old value from deployed builds and caches, and from the repository's history where you can; once the key is revoked, a copy left there no longer works. Then tell me exactly what you changed, and do not print any secret values back to me or write one into a commit message, a pull request description or a log.
Then verify: After you deploy the fix, xlogs re-scans your live app and reports whether the key is still found in what it reads. That cannot show the old key was revoked, so revoke it at the provider either way.
Full step-by-step fix guide, with a copy-paste block for each AI tool →
Common questions
Are Replit apps secure by default?
No. Replit runs and hosts your app, but it does not decide which of your keys are secret or which database tables are private. Those are choices in your code and your database config. A running Replit app can still ship a secret key to the browser.
How do I check my Replit app for exposed keys?
Paste your live Replit URL into the scanner above. It reads the JavaScript your app ships and matches it against known key formats for Stripe, OpenAI, AWS, Supabase, and more. A public key that is designed to ship is not flagged; a secret one is.