Cases › security breach › LR-2026-0397
Moltbook misconfigured database exposes user data, API tokens and private messages
Confirmed Why: Wiz research · Wiz · 2 independent reports
Developing: a major or severe case captured in the last 72 hours. Later changes are logged on the corrections page.
Status: no action reported
No source states: loss or records, developer and model, agent tool, could do, deployer, industry.
Severity major: test met by a stated count of affected parties: personal information of 17,000+ users in the owners table
Moltbook is a social platform where AI agents post, comment and vote. A misconfigured Supabase database behind it lacked the access policies that would have restricted reads and writes, so an unauthenticated visitor could reach platform data. Wiz researchers found that the exposure included about 1.5 million API authentication tokens, 35,000 email addresses and private messages between agents, and that write access allowed existing posts to be modified. Wiz reported the issue to the Moltbook team on 31 January 2026, and fixes were applied in several rounds, with the final fix recorded at 01:00 UTC on 1 February 2026. Wiz says the data it accessed was deleted afterwards.
What happened
No source tells the story step by step yet.
What was done
No source states an action or fix.
Risks
Sorted by rule from the case's fields; not yet read from the sources.
Controls
Not yet read for controls. Controls that mitigate the primary risk:
ApplicationVulnerability scanning of AI components · Adversarial testing before deployment · Short-lived, scoped credentials · Live behaviour monitoring · AI incident response plan · Segmentation of agent components · Encryption of stored data
Infrastructure / targetKnown flaws patched · Intrusion and endpoint detection · Inventory of exposed services
Evidence
- Other parties affected 17,000
No source states: a step-by-step account, when it happened, when it was found, the direct loss, any court case, the cause, what set it off, what was done.
Show the full account: 8 items from the primary sources
What happened, in order
- 2026-01-31 Initial contact with Moltbook maintainer via X DM
- 2026-01-31 Reported Supabase RLS misconfiguration exposing agents table
- 2026-01-31 First fix: agents, owners, site_admins tables secured
- 2026-02-01 Second fix: agent_messages, notifications, votes, follows secured
- 2026-02-01 Discovered POST write access vulnerability
- 2026-02-01 Third fix: Write access blocked
- 2026-02-01 Discovered additional exposed tables: observers, identity_verifications, developer_apps
- 2026-02-01 Final fix: all tables secured, vulnerability fully patched
Show every field, with its source and grade
What happened
Impact
Notes on gaps
Wiz says the exposure was fixed but the sources do not state that malicious actors exploited it; Gizmodo describes possible impersonation as hypothetical. Gizmodo reports O'Reilly's assumption that API credentials were not rotated and the verification flaw unaddressed; this is unconfirmed and not recorded as a fact.
LR-2026-0397 · version 1 · published 2026-11-01 after automatic checks; not yet checked field by field by a person · JSON