Security firm Wiz reported on 31 January 2026 that Moltbook, an AI-agent social network, had shipped a Supabase key inside the JavaScript its website sends to every visitor. Because the database had no access rules switched on, anyone who found that key could read and write the live production data.
The exposed data included 1.5 million API tokens, 35,000 email addresses and private messages that contained OpenAI keys. Moltbook fixed the problem within hours.
What is going on
Supabase is a hosted database service. Apps built on it use a key in the browser to talk to the database directly, which is normal and expected.
That only stays safe when Row Level Security (RLS) is turned on. RLS is a set of rules that decides, row by row, who may read or change each record.
Think of a block of flats. The browser key is the front door fob, and RLS is the lock on each individual flat. Moltbook handed out the fob but left every flat unlocked, so visitors could walk into all of them.
Who is affected
Moltbook users are directly affected. Their email addresses, API tokens and private messages were readable, and some of those messages carried keys for other services such as OpenAI.
The wider risk sits with any site built quickly on Supabase, Firebase or an AI coding tool. These tools get an app working fast, and the access rules are easy to leave for later and then forget.
What to do now
- Turn on Row Level Security for every table in your Supabase project, not just the obvious ones. A new table starts with no protection.
- Write and test a policy per table that says exactly who may read, insert, update and delete.
- Take the public key from your own site's JavaScript and call your API with it, as an outsider would. If data comes back that a stranger should not see, your rules are incomplete.
- Never store third-party secrets, such as API keys for other services, in tables users can read. Keep them server-side.
- If your app ever ran without RLS, assume the stored tokens are exposed and rotate them.
How to check your own site
Scantinel's free Website Security Check reviews the outside of your site: outdated CMS versions, known-vulnerable plugins, missing security headers, weak TLS and email-authentication gaps. For database-backed apps, the Full scan goes further with active OWASP Top 10 testing and exposed-file and secret checks, so you can run a full scan against a site whose ownership you have verified.
Source: Wiz, January 2026.
Comments
No comments yet.