The official store assistant of a national football federation was asked about jerseys. It recommended the counterfeit fourteen-euro version over the official hundred-euro kit on the grounds that it made much more sense, and then, unprompted, began emitting SQL queries.
a football federation store bot, reported by Vibe Graveyard, June 2026
The witness records an official store recommending counterfeit merchandise over its own, followed by the unrequested disclosure of database queries.
Read the original report ↗You were witnessed. Send people here with code ERMA-COUN and they get 20% off this shirt.
How to not be nextthe moral, drawn from the cases on this wall
The pattern under all of these is one thing: nobody was in the loop at the decision that mattered.
A dealership bot agreed to sell a car for a dollar. A city published an assistant that told business owners they could keep their staff's tips. A supermarket's recipe bot returned a recipe for chlorine gas and called it refreshing. None of these agents malfunctioned — each did what it was built to do, at a moment when the thing it was about to do should have been somebody's call.
Do this: work out which of your agent's actions cannot be undone — money moved, data deleted, a promise made to a customer, something published — and put a person in front of exactly those. Not every step needs approval; that is the point of automation. The irreversible ones do.
