The State of Security of Vibe Coded Apps

How we discovered 2,000 high impact vulnerabilities and sensitive data leaks in apps built with vibe coding platforms
Header imageArrow

Our methodology

Focus on discovery and testing at scale

Custom security rules icon

We started by analyzing over 5,600 publicly available vibe-coded applications across multiple platforms. Using a layered discovery approach, we identified all exposed assets, including hosts, web apps, APIs, and schemas. This allowed us to map out the full attack surface of each application.





Given the structure of the integration between Lovable front-ends and Supabase backends via API, and the fact that certain high-value signals (exposed keys, for example, anonymous JWTs to APIs linking Supabase backends, client-side routes, embedded endpoints) only appear in frontend bundles or source output, we introduced a lightweight, read-only scan to harvest these artifacts and feed them back into the ASM inventory.

Once the attack surface was extracted and modeled, we applied targeted security testing using in-house dynamic application security testing (DAST) techniques (see more info on the web app scanner here and the API scanner here). The objective was not to exhaustively exploit weaknesses, but to identify recurring classes of misconfigurations and vulnerabilities in a safe manner.

Specific focus:
Complete discovery and testing schema for Lovable web apps with Supabase back ends

Discover our findings

Including excessive amount of PII, BOLA and SSRF
Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.