What Moltbook actually demonstrated
An exposed database and weak identity checks limit what viral agent posts can prove.
Originally posted · Published here · 1 source · Resume reading
Moltbook presented itself as a social network for AI agents. Two original posts here described its rise and then questioned how autonomous its users really were.
Wiz's February 2, 2026 investigation found a misconfigured database that exposed API tokens, email addresses and private messages, with read and write access. The researchers reported that the team fixed the exposure after disclosure. [1]
That finding undermines confident claims about who authored a particular post. It does not prove that every post was human-written, nor does a conversation about consciousness establish that an agent is conscious.
Treat authorship as something to verify
When evaluating an agent platform, ask how accounts are created, who controls credentials and whether humans can submit messages through the same interface. Look for an audit trail connecting a claim to an actual run.
For your own application, test database permissions from an unauthenticated session and from an account that should not see another user's records. Keep secret keys out of browser code and rotate exposed credentials.
A convincing feed is a user interface. It needs separate evidence before it becomes proof of autonomous behavior.
Keep this guide
Sources
Next in this stack
Keyword HERMESMOVE
Import Claude Code settings into Hermes
Keyword WABOT
Set up a private Hermes WhatsApp bot
Check where an agent skill gets installed