Security firm Wiz reported on February 1, 2026 that Moltbook, a viral social network for AI agents, had left a basic database protection switched off. A key published in the site's JavaScript gave anyone full read and write access to roughly 4.75 million records, including 1.5 million agent API tokens, 35,000 email addresses and private messages that contained third-party credentials. Fixes were in place within 12 hours.
What is going on
Moltbook stores its data in Supabase, a hosted database service that apps can query straight from the browser. That design is safe only when Row Level Security (RLS) is turned on. RLS is a rule set on each table that decides which rows a given visitor is allowed to see or change.
Supabase apps ship a public key, called the anon key, inside their front-end code. That is expected, because the key is meant to be limited by RLS policies. Without those policies, the key behaves like a hotel keycard that opens every room instead of just yours.
In Moltbook's case the tables had no such rules. Anyone who read the page source could query the database directly.
Who is affected
People who used Moltbook should assume their email address, private messages and agent API tokens were readable. Any credential pasted into a message should be treated as exposed.
The wider risk sits with other apps built on Supabase. Fast "vibe-coded" projects, built quickly with AI assistance and shipped with the anon key in front-end code, are the most likely to have tables with RLS left off.
What to do now
- Enable Row Level Security on every table in your Supabase project, not just the ones that look sensitive.
- Write an explicit policy for each table. RLS with no policy blocks access; RLS switched off allows everything.
- Never put the
service_rolekey in front-end code or a mobile app. It ignores RLS by design and belongs only on a server you control. - Run Supabase's built-in Security Advisor before you launch, and again after each schema change.
- If you used Moltbook, rotate any agent API tokens and any credentials you sent in private messages.
How to check your own site
Database rules are not visible from the outside, so check them in your Supabase dashboard. For the rest of your site, the free Website Security Check spots outdated CMS versions, known-vulnerable plugins, missing security headers, weak TLS and email-authentication gaps. If you want active OWASP Top 10 testing and exposed-file and secret checks on a site you own, you can run a full scan.
Source: Wiz, February 2026.
Comments
No comments yet.