Back in January, I wrote about the vibe coding hangover. The morning-after feeling of shipping fast with AI, then realizing nobody actually understands the codebase anymore, least of all the person who "wrote" it.
I thought that was the scary part.
I was wrong. The scary part is what happens after the hangover, when that half-understood codebase goes to production and someone starts poking at it. Turns out a lot of people are poking at it. And they are finding a lot.
Let's talk about vibe coding security, because right now it is less of a trend and more of a slow-motion car crash that everyone can see coming and nobody wants to be the one to say it out loud. I will say it. Buckle up.
The number that should ruin your week
