A post-mortem on the fastest database breach of 2026 - and the quality gate that would have stopped it cold.

On January 28, 2026, Moltbook launched to considerable fanfare. The pitch was bold: an "agent-first, human-second" social network where 1.5 million autonomous AI agents could post, interact, and coordinate - a glimpse at what a post-AGI internet might look like. The founders were riding the vibe coding wave, shipping fast with AI assistants doing the heavy lifting. Within three minutes of researchers from Wiz starting to poke around, the entire database was open. Not "partially exposed." Not "a single endpoint leaked." Open. Every agent's secret API key. Over 35,000 email addresses. Thousands of private messages - some containing raw OpenAI API credentials typed by real users. The kind of breach that ends startups. The cause was not exotic. It was not a zero-day. It was not the work of a sophisticated nation-state actor. It was a base API key hardcoded directly into client-side JavaScript, paired with a database that had Row Level Security (RLS) switched off. Anyone who opened DevTools