Moltbook Database Exposure Allegedly Revealed Users' Private Communications and API Authentication Tokens

January 31, 2026

The incident highlights the critical importance of robust security measures in protecting sensitive user data. The exposure not only compromised users' trust but also provided a potential vulnerability for malicious actors to exploit, further emphasizing the need for vigilance and proactive defense strategies against such breaches. If you want to know more about this alarming development, check out our latest article on Moltbook database exposure JOIN US.

Matched TAIM controls

Suggested mapping from embedding similarity (not a formal assessment). Browse all TAIM controls

Alleged deployer
Moltbook platform operators, Moltbook
Alleged developer
Moltbook
Alleged harmed parties
Privacy, Moltbook users, Moltbook account holders

AI governance case studies

For forensic AI governance failure analysis (TAIMScore™ case studies), browse Human Signal’s Failure Files™.

Source

Data from the AI Incident Database (AIID). Cite this incident: https://incidentdatabase.ai/cite/1364

Data source

Incident data is from the AI Incident Database (AIID).

When citing the database as a whole, please use:

McGregor, S. (2021) Preventing Repeated Real World AI Failures by Cataloging Incidents: The AI Incident Database. In Proceedings of the Thirty-Third Annual Conference on Innovative Applications of Artificial Intelligence (IAAI-21). Virtual Conference.

Pre-print on arXiv · Database snapshots & citation guide

We use weekly snapshots of the AIID for stable reference. For the official suggested citation of a specific incident, use the “Cite this incident” link on each incident page.