Moltbook Database Leaked, 4.75 Million User Records Exposed Due to Insecure Configuration

A significant security incident has affected the AI-based forum Moltbook, when misconfigured server settings led to widespread exposure of their database. The database is the core of each platform’s data storage system, and in the case of Moltbook, millions of sensitive user information records were accessed without authorization. According to a report from PANews, this leak involves large amounts of data that should have been tightly protected.

What Happened to the Database Is a Misconfiguration That Poses a Threat

The main cause of this incident is a configuration issue in Moltbook’s infrastructure, a technical mistake that often occurs when database security settings are not properly configured. An unlocked database allows public access without authentication, making the entire data repository vulnerable to intrusion. This security flaw becomes even more dangerous considering Moltbook stores information from millions of users who use the platform for discussions about artificial intelligence.

What Sensitive Data Was Exposed from the Moltbook Database

The scope of this leak is extensive, involving 4.75 million records that were accessed unlawfully. Among the exposed data from the Moltbook database are 1.5 million API authorization tokens used to access third-party services, 35,000 user email addresses that could be used for phishing attacks, 20,000 email records containing private communications, and several OpenAI API keys that, if misused, could cause significant financial losses. This combination of data creates a layered threat to user security and the overall integrity of the platform.

Security Steps Users Should Take Immediately

Given the risks posed by the exposed database, Moltbook users should take immediate protective actions. First, audit all your accounts on the platform and other connected platforms that hold information from Moltbook. Second, change all passwords related to your Moltbook account and services using the same credentials. Third, if you have API keys or authentication tokens, promptly rotate or regenerate those tokens to eliminate compromised access. Finally, regularly monitor your account activity and consider enabling two-factor authentication as an additional security layer to prevent unauthorized access in the future.