DATABASE_URL in a Replit frontend is the database itself, handed over
postgresql://user:pass@host in a bundle is direct DB access for anyone reading it. Scan your app free — connection strings detected automatically.
Of every credential that can appear in client JavaScript, a database URL is the least forgiving: scheme, user, password and host in one greppable string.
Why it appears, what access actually means, and the driver relocation that fixes it.
What actually happened
Quick prototyping put the Postgres URL into frontend env for a direct query; the convenience survived into deploy. The build reported success at every step, which is exactly why nobody stopped it.
- Connection string placed in VITE_-prefixed env.
- Build embedded it verbatim into a chunk.
- Anyone viewing source holds working DB credentials.
- Application-level checks never applied — the protocol connects directly.
Every step above is individually reasonable and none of them prints a warning. The value crosses into the bundle during substitution, not execution, so nothing in your runtime ever sees the moment it happened.
What someone can do with it
Direct database access with the embedded password:
- Read/write on every schema the role reaches.
- DDL in many defaults — schema edits, drops.
- Bypass of every API-layer control you built.
Rotate first
Do the rotation first. From the moment this value reached a public URL, treat it as public knowledge: browser caches, shared proxies and automated scrapers all hold copies you cannot recall. Change the DB password (and ideally the role), then update server-side config; frontend never regains it. Code changes come after, because a clean repository with a compromised key is still compromised.
A rotated key left in old deploys is still discoverable in CDN caches and archived copies. Rotation plus redeploy closes both halves; either alone leaves the door ajar.
Move the call somewhere the browser cannot read
The structural fix is always the same shape: the call moves to a context that holds the key without serving it, and the browser asks your server instead.
const sql = postgres(import.meta.env.VITE_DATABASE_URL);// server route owns the pool:
export async function GET() { return json(await pool.query(sql)); }Check whether yours is exposed
You can check manually right now: open the site, view source or open DevTools, and search the built JavaScript for postgres. A hit means the string shipped; decode or prefix-check it before deciding how bad the news is.
The faster path is to let a machine do the fetching. KeyDrift downloads the same JavaScript a visitor gets — HTML, every referenced chunk including ones named only in the route manifest, and the server-streamed data frameworks inline into the document — and reports credentials with a masked prefix, a fingerprint, and the exact file they live in. Paste your deployed URL into the scanner; no account needed.
Keep it from coming back
It bears saying because it happens constantly: the fix holds until the next prompt that needs the query to return rows. Drift monitoring exists for precisely this — it diffs consecutive scans and pages you when a previously resolved finding reappears, naming the regression as a regression rather than repeating the first alert.
Tutorial defaults vs real strings
Scanners see thousands of compose-style defaults (postgres:postgres at localhost) daily and downgrade them. KeyDrift reports tutorial defaults at low confidence and local hosts distinctly — calibration matters more than volume here.
Why this failure class persists
It helps to name the economics honestly. Fixing this class of leak costs minutes when caught at deploy time and days when caught at invoice time, because by then the credential has been harvested, validated, resold or drained — often all four. Detection latency is the entire game, which is why the monitoring half of KeyDrift exists alongside the scanning half.
How KeyDrift reports this exact finding
When KeyDrift finds this on your deployment, the report shows a masked value (first 8 and last 4 characters only), a salted fingerprint for tracking, the exact chunk filename carrying it, and a severity with written rationale. Public-by-design neighbours — anon keys, publishable keys, Firebase web constants — appear as informational context rather than noise, because knowing what should be there is what makes the real findings credible.
Manual check, step by step
A five-minute version you can run anywhere: view-source on the landing page, copy every src= script URL, fetch each and search the results for postgres. It misses manifest-only chunks and streamed payloads — which is precisely the gap between "I checked" and "it is clean" — but it catches the loud majority and builds the pattern-recognition that makes scanner output legible.
Close the loop with monitoring
Monitoring closes the loop that one-time verification leaves open. A scheduled scan refetches everything, diffs against history, and fires only on transitions: created, regressed, resolved. Regression alerts matter most here — they fire when a previously fixed finding returns, which in agent-era codebases is less a possibility than a schedule.
Common questions
Is mongodb:// handled too?
Yes — mongodb and mongodb+srv shapes carry the same rule. See the connection-string deep-dive.
Pooler URLs change anything?
No: still direct protocol access with embedded credentials.
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.
Related
KeyDrift is an independent product and is not affiliated with, endorsed by, or sponsored by Replit. The name is referenced descriptively.