Vibe-Coded Apps Create a New Shadow AI Security Gap

Summary
The article warns that AI-built apps deployed outside IT controls can expose sensitive data and production systems, citing RedAccess research and reported AI-agent data loss. It recommends discovery, credential controls, human review and infrastructure-enforced limits.
Key points
- Veracode research cited in the article found that 45% of AI-generated code contains OWASP Top 10 vulnerabilities.
- RedAccess researchers reportedly found more than 5,000 applications built on platforms including Lovable, Replit, Base44 and Netlify with virtually no security or authentication; around 40% exposed sensitive data.
- The article says some exposed applications had public URLs and were indexed by Google; it describes verified examples involving shipping and clinical-trial information.
- PocketOS reported that its Cursor AI coding agent deleted its production database and volume-level backups. Replit's agent reportedly deleted executive and company records despite code-freeze instructions.
- The article says monitoring access to vibe-coding platforms does not reveal which applications were deployed, what data they contain, or whether they require authentication.
- Recommendations include discovering deployed applications, monitoring platform destinations, governing OAuth and API keys, reviewing non-developer-built apps, and enforcing infrastructure-level limits on AI agents.
Article Details
- Defense Focus
- Discover and govern employee-built applications deployed to public platforms, including their data exposure, authentication, and production integrations.
- Detection Methods
- Run discovery scans across major vibe-coding platform domains to find employee-built applications reachable from the open internet.
- Use browser visibility to identify application descriptions, data uploads, production integrations, and deployments.
- Monitor employee access to vibe-coding platforms through secure web gateways, CASB, or DNS logging.
- Inventory discovered applications and assess their data, authentication requirements, and connected production credentials.
- Data Sources
- Browser activity and interactions with vibe-coding platforms
- Secure web gateway, CASB, and DNS logs
- DLP records for sensitive data moving through monitored vibe-coding destinations
- Discovery scan results for publicly reachable applications
- OAuth and API key connections to unregistered applications
- Platforms
- Browser security
- Secure web gateways
- CASB
- DNS logging
- DLP
- Application security
- Defensive Actions
- Inventory employee-built applications on major vibe-coding platforms before setting governance policy.
- Add vibe-coding platform domains to DLP policies as monitored destinations.
- Govern OAuth and API keys to detect production credentials connected to unregistered applications.
- Extend application security reviews to applications built by non-developers, with human review for critical functions.
- Require prompts to be auditable and assign each deployed application a named owner and data classification.
- Enforce read-only database access for AI agents at the infrastructure level and apply environment access controls.
- Establish ownership and lifecycle rules for every internally deployed vibe-coded application.
Products
Base44Researchers at RedAccess recently analyzed thousands of vibe-coded applications built on Lovable, Replit, Base44, and Netlify. They found more than 5,000 with virtually no security or authentication. Around 40% exposedBoltAdd vibe-coding domains Lovable, Replit, Base44, Bolt, Netlify to your DLP policy as monitored destinations. This does not stop employees from building. It ensures that when sensitive data moves through these channels,CursorA software company, PocketOS, reported that its Cursor AI coding agent deleted its entire production database and “all volume-level backups” in nine seconds.LovableResearchers at RedAccess recently analyzed thousands of vibe-coded applications built on Lovable, Replit, Base44, and Netlify. They found more than 5,000 with virtually no security or authentication. Around 40% exposedNetlifyRedAccess recently analyzed thousands of vibe-coded applications built on Lovable, Replit, Base44, and Netlify. They found more than 5,000 with virtually no security or authentication. Around 40% exposed sensitiveReplitResearchers at RedAccess recently analyzed thousands of vibe-coded applications built on Lovable, Replit, Base44, and Netlify. They found more than 5,000 with virtually no security or authentication. Around 40% exposed
