How to Fix Replit API Key Exposure (2026)

In our scans of Replit-deployed apps, hardcoded API keys appeared in 58% of flagged projects. That rate is higher than Bolt.new or Netlify deployments, and the cause is consistent: Replit Agent writes API calls with the key value inline instead of referencing process.env. The app works immediately, the leak is invisible unless you look at the source, and if the Repl is public (the default), anyone who visits the Repl URL can click Files and read the key directly.

This guide walks you through finding the leak, rotating the key, and moving secrets to the Replit Secrets tab so they never appear in your source files again.

Why Replit Exposure Is Different

Unlike Bolt.new or Lovable apps where the problem is usually a VITE_-prefixed variable baked into a browser JavaScript bundle, Replit apps are typically server-side Node.js, Python, or Express apps. The exposure is simpler: the key is written into a .js or .py file, and that file is readable by anyone who can view your Repl.

Two things make this especially risky:

Public Repls expose source code. A new Repl is public by default. Anyone who finds or guesses your Repl URL can click the Files panel and read every source file. There is no build process to obscure the value.

Replit Agent writes working code immediately. When Agent adds an OpenAI integration, it sometimes echoes the key value from your conversation context into the code directly. The result runs on the first try, so there is no obvious error prompting a review.

Step 1: Find the Exposed Key

# Search for common key prefixes hardcoded in source files
grep -rn "sk-proj-\|sk-ant-\|sk_live_\|rk_live_\|AKIA\|eyJhbGci" . \
  --include="*.js" --include="*.ts" --include="*.py" --include="*.jsx" --include="*.tsx" \
  --exclude-dir=node_modules --exclude-dir=.git

# Also search for generic inline key assignments
grep -rn "apiKey.*=.*['\"][A-Za-z0-9_\-]\{20,\}" . \
  --include="*.js" --include="*.ts" --include="*.py" \
  --exclude-dir=node_modules

# Check if .env was ever committed
git log --all --full-history -- .env
git log --all --full-history -- .env.local

Step 2: Rotate the Exposed Key Immediately

Do not fix the code first. The key is already out. Rotate it now.

Step 3: Remove the Key from Source Files

Now update your code to use the Replit Secret instead of the hardcoded value.

Node.js

Wrong (key hardcoded by Replit Agent):

// main.js - Replit Agent wrote this inline
const OpenAI = require('openai');
const client = new OpenAI({
  apiKey: 'sk-proj-abc123...',  // visible in source, must be removed
});

Right (reads from Replit Secrets at runtime):

// main.js - reads from Secrets tab, never in source
const OpenAI = require('openai');
const client = new OpenAI({
  apiKey: process.env.OPENAI_API_KEY,  // set this in Tools > Secrets
});

Python

Wrong:

# main.py - hardcoded by Agent
import openai
client = openai.OpenAI(api_key="sk-proj-abc123...")

Right:

# main.py - reads from Replit Secrets
import os
import openai
client = openai.OpenAI(api_key=os.environ.get("OPENAI_API_KEY"))

How to Set Secrets in Replit

1. Click Tools in the left sidebar (or the lock icon).
2. Click Secrets.
3. Click + New Secret.
4. Enter the variable name: OPENAI_API_KEY.
5. Paste the key value.
6. Click Add Secret.

The secret is now available as process.env.OPENAI_API_KEY (Node.js) or os.environ.get('OPENAI_API_KEY') (Python) every time your Repl runs.

Step 4: Remove from Git History (if connected to GitHub)

If your Repl is connected to a GitHub repository and the key was committed there, clean the history.

# Install git-filter-repo
pip install git-filter-repo

# Remove .env from all history
git filter-repo --path .env --invert-paths
git filter-repo --path .env.local --invert-paths

After scrubbing, force-push to all remotes. If the GitHub repo was public at any point, treat the key as compromised.

Also add .env to .gitignore:

echo ".env" >> .gitignore
echo ".env.local" >> .gitignore
git add .gitignore && git commit -m "chore: gitignore .env files"

Step 5: Check Repl Visibility

After cleaning the code, decide on the right visibility setting for your Repl.

• Private: Only you (and collaborators you invite) can view the source. Choose this for production apps.
• Public: Anyone can view your source code by visiting the Repl URL. Fine for demos or open-source projects, but never with hardcoded secrets.

To change visibility: click your Repl name at the top > Settings > Privacy > set to Private.

Note: Changing to Private now does not undo exposure that happened while it was Public. If the Repl was public with a hardcoded key, rotate the key regardless.

Step 6: Prevent Future Leaks from Replit Agent

Replit Agent generates functional code, but it sometimes writes secrets inline. You can reduce this with explicit prompting.

Add an instruction at the start of your Agent conversation:

"For any API keys or secrets this app needs, store them in Replit Secrets (process.env.SECRET_NAME in Node.js, os.environ.get('SECRET_NAME') in Python). Never hardcode key values in source files."

After Agent generates any code involving an external API, run this check before saving:

grep -rn "sk-proj-\|sk-ant-\|sk_live_\|AKIA" . \
  --include="*.js" --include="*.ts" --include="*.py" \
  --exclude-dir=node_modules

If this returns any matches with actual key values, replace them with process.env references before the code goes live.

What Goes Where

The Supabase anon key is designed to be public and safe to use in browser code (protected by RLS). Everything else belongs in Secrets.