Vibe coding was coined as a term for throwaway weekend projects. The kind of thing you build for yourself, run locally, and never expect another person to touch. Then Moltbook happened.
According to a piece by Nazmul Hasan, a project called Moltbook leaked 1.5 million API tokens. That is not a misconfigured environment variable on a solo dev’s laptop. That is a real exposure with real downstream consequences.
Where the Line Actually Is
Hasan puts the boundary in one sentence worth keeping:
The line isn’t how big the codebase gets. It’s the first stranger who types an email address into it.
That framing is useful. Most vibe-coded tools start with zero security assumptions because they were never meant to handle anyone else’s data. The moment a real user enters credentials or connects an account, those assumptions become a liability.
The Operator Takeaway
If you are shipping anything AI-assisted, ask one question before you share the link: will someone who is not you ever authenticate into this? If yes, the security bar is no longer a weekend project bar. API key handling, token storage, and access scoping are not optional once real users are in the loop.
The full writeup is on Medium. Worth reading before you push your next side project to production.
