People search Supabase data breach timeline because the brand sits on billions of accounts, credentials, and cloud workloads. BreachHistory indexes 2 Supabase-linked incidents, with headline counts up to 1.5M+ in catalog rows. This page maps every attested event through 2026 with internal links to canonical records.
Why Supabase breach history matters
Supabase operates in Technology (United States). Across indexed rows, recurring themes include cloud and database misconfiguration. Understanding the chronological pattern helps security teams, customers, and regulators separate confirmed disclosures from forum marketing.
Full timeline through 2026
2026 — Moltbook RLS disabled, 1.5M tokens, 35k emails exposed
Cataloged incident. Moltbook, an AI social network built on Supabase, suffered a major breach due to disabled Row Level Security. Wiz researchers found the production database publicly accessible with full read/write via exposed client-side API key. Exposed: 1.5M agent auth tokens (complete account takeover), 35k+ user emails, 4,060 private messages, OpenAI/Anthropic API keys. Caused by customer misconfiguration, not Supabase vulnerability. Platform taken offline to reset keys. Exposed categories include 1.5M auth tokens; 35k+ emails; private messages; third-party API keys. BreachHistory cites approximately 1.5M+ affected records in this row. See the supabase2026-moltbook and canonical BreachHistory entry.
2024 — RLS misconfiguration, thousands of instances
Cataloged incident. Widespread: missing Row-Level Security leaves anon key as master key. Attackers dump databases via REST API. CVE-2025-48757 affected 170 Lovable apps. MCP data leak July 2025: AI agents with service_role keys bypass RLS. Exposed categories include Full database access; user data; API keys; payment data. No attested victim count is published for this row yet. See the supabase2024 and canonical BreachHistory entry.
Patterns and analysis
- Cloud and database misconfiguration — appears across multiple Supabase catalog entries; prioritize controls that address this class of failure.
- Record-count hygiene — BreachHistory indexes actor-cited figures separately from company-confirmed totals; read each row's technicalWriteup before treating counts as fact.
- 2026 monitoring — New disclosures roll into this timeline as they are verified or labeled unverified per catalog policy.
What to do if you may be affected
- Step 1: Enable phishing-resistant MFA on every account tied to this brand.
- Step 2: Use unique passwords and a password manager—breach rows often involve credential reuse.
- Step 3: Monitor official company breach notices and regulator filings, not dark-web downloads.
- Step 4: Review OAuth app permissions and revoke unused third-party integrations.
- Step 5: Bookmark the Supabase company page for new 2026+ disclosures.
Canonical BreachHistory hub
Explore every indexed row: breachhistory.com/supabase · Latest: supabase2026-moltbook.
Sources: BreachHistory catalog (2 rows for Supabase), company and regulator disclosures cited in individual breach records.