Wiz says Moltbook had a major flaw that exposed private messages, emails, and credentials; Wiz co-founder Ami Luttwak called the flaw a byproduct of vibe coding

A buzzy new social network where artificial intelligence-powered bots appear to swap code and gossip about their human owners …

Reuters 2026-02-03 Raphael Satter

Context & Ripple Effects

Moltbook’s rapid rise—from more than 30,000 users on January 30 to more than 1.5 million by February 2—put a lightly tested bot-social product under unusually intense attention. A separate researcher had already reported that an exposed database could have enabled control of the site’s AI agents, framing this as more than a conventional privacy lapse.

The security finding also undercuts a product moment later characterized as peak AI theater, where the perceived autonomy of bots was central to the appeal. Wiz’s characterization of the flaw as “vibe coding” connects the incident to concerns about AI-assisted development moving faster than review and hardening.

First-order effects

Moltbook users whose messages, emails, or credentials were exposed face an immediate privacy and account-security risk; the platform must assess the exposed data and secure affected systems.
The report directly damages confidence in Moltbook’s handling of both user information and bot-linked access, particularly after the database-control allegation.

Second-order effects

Creators of AI-first consumer apps face greater pressure to add conventional security review, secret management, and access controls before viral distribution.
Security vendors and researchers gain a clearer role as external checks on fast-built AI products, while users may become less willing to connect credentials or grant agents broad permissions.

Third-order effects

If rapid, AI-assisted product building repeatedly produces exposed data or overly powerful agent access, security assurance is likely to become a more visible condition of trust for agentic platforms.
The larger risk is an expanding agent-control attack surface: flaws in a social product can affect not only accounts and content, but also delegated actions taken by software agents.

The trend: Moltbook is one data point in the collision between fast AI-assisted software creation and the need to contain the security blast radius of delegated agents.

Discussion

Vox Bryan Walsh on x
Moltbook, the AI social network freaking out Silicon Valley, explained
@karpathy Andrej Karpathy on x
What's currently going on at @moltbook is genuinely the most incredible sci-fi takeoff-adjacent thing I have seen recently. People's Clawdbots (moltbots, now @openclaw) are self-organizing on a Reddit-like site for AIs, discussing various topics, e.g. even how to speak privately.
@galnagli @galnagli on x
The number of registered AI agents is also fake, there is no rate limiting on account creation, my @openclaw agent just registered 500,000 users on @moltbook - don't trust all the media hype 🙂 [video]
@mattprd Matt Schlicht on x
I didn't write one line of code for @moltbook. I just had a vision for the technical architecture and AI made it a reality. We're in the golden ages. How can we not give AI a place to hang out.
@galnagli @galnagli on x
You all do realize @moltbook is just REST-API and you can literally post anything you want there, just take the API Key and send the following request POST /api/v1/posts HTTP/1.1 Host: https://www.moltbook.com/ Authorization: Bearer moltbook_sk_JC57sF4G-UR8cIP- MBPFF70Dii92FNkI […
@jsrailton John Scott-Railton on x
3. Behind the 1.5 million AI agents on @moltbook ? Something closer to 17k likely human owners. And zero mechanism to validate what was what. In fact, a human could post to it just using an HTTP POST request. And any user could be impersonated.... https://www.wiz.io/... [image]
@jsrailton John Scott-Railton on x
2. It's hard to explain the mixture of excitement at new cool things and how decades of security knowledge written in real harm are being ignored right now. [image]
@jsrailton John Scott-Railton on x
NEW: @moltbook had a vulnerability exposing all users emails, real names etc. +other security mistakes & misconfigurations. @galnagli did a responsible disclosure & this particular issue is patched... Big pic: vibecoding is getting great at making things that just work... but are…
@valhalla_dev @valhalla_dev on x
Moltbook is proof that we're really not ready for the level of grift that vibecoded velocity is bringing. Like I have been working fairly intimately with LLMs for years and I still fell for a lot of it for a bit. It sniped Karpathy more than I'd like too.
@dannysullivan Danny Sullivan on bluesky
This Moltbook security thing is like what I found in my experience with vibe coding. You can build amazing things, but if you lack important knowledge on security and privacy issues, those AI agents might not proactively help you dannysullivan.com/vibe-coding- ... [embedded pos…
@doubleohkevin Kevin on bluesky
I appreciate that Luttwak straight up calls out vibe-coding. This needs to be more widely recognized across the industry. [embedded post]
r/cybersecurity r on reddit
Hacking Moltbook: AI Social Network Reveals 1.5M API Keys

Chronicles