SEC-006critical SeverityHardcoded Secrets & Credential Exposure
No NEXT_PUBLIC_ or VITE_ Prefixes on Private Secrets
When an environment variable is undefined in client code, agents prefix it with NEXT_PUBLIC_ without recognizing it exposes private secrets.
1-Click Fix Prompt for Cursor & Claude Code
Review my codebase for "No NEXT_PUBLIC_ or VITE_ Prefixes on Private Secrets" (SEC-006). Issue: When an environment variable is undefined in client code, agents prefix it with NEXT_PUBLIC_ without recognizing it exposes private secrets. Remediation required: Audit all NEXT_PUBLIC_ and VITE_ prefixed environment variables to confirm none contain secret tokens or private keys. Please: 1. Locate any occurrences of this issue across my repository. 2. Refactor the code to follow production standards without breaking existing functionality. 3. Provide a clear command or step to test and verify the fix.
Why AI Assistants Write This Bug
When an environment variable is undefined in client code, agents prefix it with NEXT_PUBLIC_ without recognizing it exposes private secrets.
AI code generation prioritizes immediate syntax execution over production edge cases. When an assistant hits an undefined variable or strict type error, it frequently takes the path of least resistance rather than implementing standard pre-launch security patterns.
Code Comparison
Common AI Code PatternVulnerable
// Vulnerable AI-generated pattern for: No NEXT_PUBLIC_ or VITE_ Prefixes on Private Secrets
// Leaking sensitive key in client-callable code
export const STRIPE_KEY = "sk_live_51OzRealProductionKey12345";
export async function checkout() {
// Client bundle exposes secret key to Chrome DevTools
}Launch-Ready Fix
// Production-ready fix for: No NEXT_PUBLIC_ or VITE_ Prefixes on Private Secrets
// Stored strictly in server-side environment variable
const stripeSecretKey = process.env.STRIPE_SECRET_KEY;
if (!stripeSecretKey) {
throw new Error("Missing STRIPE_SECRET_KEY in server environment");
}
// Invoked strictly inside server route or Server Action
export const stripe = new Stripe(stripeSecretKey);Remediation & Verification Checklist
Remediation: Audit all NEXT_PUBLIC_ and VITE_ prefixed environment variables to confirm none contain secret tokens or private keys.
- Search your codebase for pattern matching "No NEXT_PUBLIC_ or VITE_ Prefixes on Private Secrets".
- Apply the recommended remediation: Audit all NEXT_PUBLIC_ and VITE_ prefixed environment variables to confirm none contain secret tokens or private keys.
- Run local build and test commands to ensure no regressions.
- Verify in your browser or with curl that the issue is resolved.
Audit All 108 Checks in One Click
Checking items one by one takes hours. Let us do it in 2 minutes.
With the Founder Pass ($15 one-time), we automatically scan your repository for this issue, plus all other 107 launch checks across secrets, Stripe webhooks, Supabase RLS, and security headers.