Supabase Data Breach History
WebsiteSupabase is an open-source Firebase alternative providing Postgres database, authentication, realtime, and edge functions.
This page shows all data breaches of Supabase. View the complete breach timeline, records exposed, root causes, and AI breach risk score. BreachHistory tracks disclosed data breaches worldwide.
Data Breach Timeline — All Supabase Breaches
- 2026 2026 Supabase — Moltbook RLS disabled, 1.5M tokens, 35k emails exposed 1.5M records Share
- 2024 2024 Supabase — RLS misconfiguration, thousands of instances Unknown records Share
Supabase Data Breach Summary
This page tracks the Supabase data breach history and cybersecurity incidents affecting Supabase (United States). BreachHistory currently indexes 2 publicly disclosed or catalogued incidents spanning 2024 through 2026, with approximately 1.5 million records reported as exposed across all indexed events. These totals may include overlapping datasets or third-party estimates and should not be interpreted as unique affected users.
The Supabase breach timeline includes major data breaches, cyber attacks, data leaks, credential exposures, API abuse, and other security incidents. Each incident provides details on the estimated records exposed, attack method, affected data types, and supporting public sources. Currently, 0 incidents are company-confirmed.
Largest Supabase Data Breaches
The largest indexed incidents include the 2026 Supabase — Moltbook RLS disabled, 1.5M tokens, 35k emails exposed. Record counts originating from threat actors or leak sites should be treated as estimates unless confirmed by Supabase or a regulator. Below is the list of large data breaches:
- 2026 2026 Supabase — Moltbook RLS disabled, 1.5M tokens, 35k emails exposed — about 1.5M records exposed · Catalogued incident
What Information Was Exposed?
Depending on the incident, exposed data may include email addresses, payment card and financial account data, private messages and communications, and other personal information (PII). The exact data varies between incidents, so review each breach page before assuming your information was affected.
Supabase Data Breach 2026
At the time of this update, BreachHistory catalogues 1 2026 incident related to Supabase. Most recent entry: 2026 Supabase — Moltbook RLS disabled, 1.5M tokens, 35k emails exposed. New incidents are added as official disclosures, regulatory filings, or credible cybersecurity reports become available.
What To Do If You Were Affected
If you believe your account may have been involved in a Supabase data breach, change any reused passwords, enable multi-factor authentication (MFA), monitor your account for suspicious activity, and be cautious of phishing emails or fake breach notifications.
This Supabase breach history is maintained by BreachHistory using public disclosures, regulatory filings, security research, and clearly labelled third-party claims. For the complete breach timeline, records exposed, incident details, and AI Breach Risk Score, explore the sections on this page.