Replit Secrets and the postgres connection string that ended up in your bundle

Why Replit does this

Replit Secrets are injected as environment variables at build time. A secret that gets a `VITE_` prefix so the frontend can "see" it stops being a secret — the prefix is the mechanism that copies it into the bundle.

Confirm it first

Before rotating anything, check whether the key is actually being served. Paste your deployed URL — KeyDrift downloads the same JavaScript a visitor gets and tells you what is in it.

Rotate the key

Do this before changing any code. The key has been served to browsers, cached by CDNs and very likely scraped already — removing it from the source does not un-publish it.

1. 1Change the password on the database user immediately.
2. 2Check for tables you do not recognise and rows you did not write.
3. 3Put the database behind an API. A browser should never hold a connection string.

Move the call to a server

The replacement key must not follow the old one into the bundle, which means the code that uses it cannot live in the browser. Any variable named VITE_… is inlined at build time by design — the prefix is the mechanism, not a mistake.

// src/components/Chat.tsx
// Vite substitutes the literal value here at build time.
const key = import.meta.env.VITE_DATABASE_URL;
const result = await sql`select * from ${table}`;

// supabase/functions/query/index.ts  — runs on the Express server in the same Repl
Deno.serve(async (request) => {
  const key = Deno.env.get('DATABASE_URL')!; // never sent to the browser
  const result = await sql`select * from ${table}`;
  return Response.json(result);
});

// src/components/Chat.tsx
const result = await fetch('/functions/v1/query', { method: 'POST' }).then((r) => r.json());

How KeyDrift detects it

Matches a `postgres://` or `postgresql://` URL carrying a password. Strings using well-known tutorial credentials, or pointing at localhost, are reported lower — the password is still exposed, but the database probably is not.