SEC-003critical SeverityHardcoded Secrets & Credential Exposure
Database Connection URIs Hidden from Client Bundles
Agents often configure Prisma or Postgres pools inside shared utility files imported by both client and server code.
1-Click Fix Prompt for Cursor & Claude Code
Review my codebase for "Database Connection URIs Hidden from Client Bundles" (SEC-003). Issue: Agents often configure Prisma or Postgres pools inside shared utility files imported by both client and server code. Remediation required: Ensure postgres:// or mongodb+srv:// connection strings are kept in server-only modules never imported by client components. 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
Agents often configure Prisma or Postgres pools inside shared utility files imported by both client and server code.
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: Database Connection URIs Hidden from Client Bundles
// 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: Database Connection URIs Hidden from Client Bundles
// 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: Ensure postgres:// or mongodb+srv:// connection strings are kept in server-only modules never imported by client components.
- Search your codebase for pattern matching "Database Connection URIs Hidden from Client Bundles".
- Apply the recommended remediation: Ensure postgres:// or mongodb+srv:// connection strings are kept in server-only modules never imported by client components.
- 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.