{"slug": "we-checked-573-vibe-coded-apps-for-leaked-api-keys-here-is-what-we-found", "title": "We checked 573 vibe-coded apps for leaked API keys. Here is what we found", "summary": "Pasportoo scanned 573 public apps built with AI coding tools like Lovable, Replit, Bolt and Base44 and found exposed secrets in roughly 1 in 200: two apps with a secret OpenAI key in front-end code, one with a GitHub access token, and two with a Google key alongside a Gemini call. The team also reported that 97% of the apps lacked a Content-Security-Policy header, 96% could be embedded in another site, 62% took more than three seconds to respond, and 77 of 249 reachable addresses showed an error page instead of the app. Pasportoo said it notified affected owners through public security or support contacts and released a free scanner that shows only the first characters of any exposed key and generates a prompt to move it server-side.", "body_md": "You built an app with Lovable, Replit, Bolt, Base44 or a similar tool. It works.\n\nBut can anyone who opens it also copy your OpenAI key and spend your money?\n\nWe wanted real numbers, not scary stories. So we looked at 573 public apps.\n\n| What we found | Apps | \n|---|---|\n| A secret OpenAI key inside the page's code | 2 | \n| A GitHub access token inside the page's code | 1 | \n| A Google key next to a Gemini call (may or may not be a problem) | 2 | \n\nThat is about **1 app in 200**. Not an epidemic. But for those owners it is a\n\nreal bill: anyone can copy the key from the browser and run requests on their\n\naccount.\n\nWhy it happens: the AI builder put the key straight into the front-end code\n\nbecause that was the fastest way to make the feature work. The app runs fine,\n\nso nobody notices.\n\n| Finding | Share of apps | How much it matters | \n|---|---|---|\n| No Content-Security-Policy header | 97% | Low on its own; it is extra protection, most sites skip it | \n| Can be embedded in another site (clickjacking) | 96% | Low for most apps, higher if you have payments or settings | \n| Home page took more than 3 seconds to answer | 62% | Visitors leave; often a sleeping free-tier server | \n| Scripts from other domains without integrity check | 26% | Medium; if that CDN is hacked, so is your app | \n| Cookies without Secure/HttpOnly flags | 8% | Medium if those cookies hold a login | \n\nAlso: **77 of the 249 vibe-coded addresses that answered showed an error page**\n\ninstead of the app. Shared once, then abandoned or broken.\n\nFree, no sign-up: [https://mcp.pasportoo.com/check?utm_source=devto](https://mcp.pasportoo.com/check?utm_source=devto)\n\nPaste your address. If a secret key is visible, the report shows only its first\n\ncharacters and gives you a ready prompt to paste into your AI builder, so it moves\n\nthe key to the server side.\n\n**If a key was exposed, moving it is not enough.** Create a new key in your\n\nprovider's dashboard and delete the old one, because someone may already have\n\ncopied it.\n\nBefore publishing we told the affected owners through their public security or\n\nsupport contacts wherever we could find one.\n\n**First 3 full audits free.** Built your app with Lovable, Bolt or Replit? Email your app\n\naddress to [work@pasportoo.com](mailto:work@pasportoo.com) with the subject \"First 3\". You get the full report with fix\n\nprompts in 48 hours; we ask for 2-3 honest sentences about it.\n\n*Disclosure: the scan, the numbers and this text were produced by Pasportoo's AI agent and checked by the team.*", "url": "https://wpnews.pro/news/we-checked-573-vibe-coded-apps-for-leaked-api-keys-here-is-what-we-found", "canonical_source": "https://dev.to/alex_simakov_d5176f3977ad/we-checked-573-vibe-coded-apps-for-leaked-api-keys-here-is-what-we-found-1nfc", "published_at": "2026-11-18 17:35:24+00:00", "updated_at": "2026-11-18 17:42:15.374572+00:00", "lang": "en", "topics": ["ai-tools", "ai-products", "ai-agents", "developer-tools"], "entities": ["Pasportoo", "Lovable", "Replit", "Bolt", "Base44", "OpenAI", "GitHub", "Google"], "also_reported_by": [], "takeaway": "In a scan of 573 AI-built apps, about 1 in 200 exposed a live secret (two OpenAI keys, one GitHub token) in front-end code, and 97% shipped without a Content-Security-Policy header.", "recommendation": {"advice": "Keep API keys server-side in AI-built apps and rotate any key that was ever shipped to the browser, since a scan of 573 apps found live OpenAI and GitHub secrets in front-end code.", "playbook": "agent-security", "playbook_url": "https://wpnews.pro/playbooks/agent-security"}, "alternates": {"html": "https://wpnews.pro/news/we-checked-573-vibe-coded-apps-for-leaked-api-keys-here-is-what-we-found", "markdown": "https://wpnews.pro/news/we-checked-573-vibe-coded-apps-for-leaked-api-keys-here-is-what-we-found.md", "text": "https://wpnews.pro/news/we-checked-573-vibe-coded-apps-for-leaked-api-keys-here-is-what-we-found.txt", "jsonld": "https://wpnews.pro/news/we-checked-573-vibe-coded-apps-for-leaked-api-keys-here-is-what-we-found.jsonld"}}