16,000 Supabase Databases Left Wide Open: The Hidden Security Cost of Vibe-Coded Apps
IPWhois.net Blacklist ipwhois.net
Read from a public source earlier. Its current version may differ.
Somewhere in the northeastern United States, a valet parking company runs its customer database on Supabase. Until recently, anyone who knew where to look could read it. Over 100,000 customers, their phone numbers, around 78,000 license plates, visit histories, how much each person tipped, and a free-text notes field where staff wrote whatever they wanted about you. Nobody hacked it. Nobody broke anything. The database simply answered every question it was asked, from anyone, because nobody told it not to.
That valet service is one of 16,326 Supabase databases that security firm UpGuard found exposing readable data in research published on September 25, 2026. Over half of them contained indicators of personal information. A smaller share leaked passwords and authentication tokens. A handful exposed what looked like payment card data. The common thread running through almost all of them was not a bug in Supabase. It was the way the apps on top of it were built: fast, by AI coding agents, often by people who never looked at the database configuration at all.
Open on another device
Scan to open this page. Your saved notes and account access are not included.