Agent chaosAs reported·19 Oct 2026
Developer blames Codex for a leaked .env and a $90,000 Google bill
As reported One person’s public account. We couldn’t independently confirm it, and we’ll update this if the facts change.
A developer says Claude Opus 5.5 traced their $90,000 Google bill to Codex publishing their .env file on Cloudflare Pages.
This is one developer's account on X, not independently confirmed. Nobody outside has seen the repo, the deploy or the full bill.
The story, as they tell it
On 10 October the developer posted that someone had stolen their keys and run swarms of fable-5.1-max on them after they passed out during a livestream coding session. Their screenshot shows a cost table with an estimated cost of about $88,983 against an expected $0.
Five days later they said they'd found the leak. Claude Opus 5.5 told them Codex had published their .env file, where projects keep secret keys, to Cloudflare Pages, which serves files to the public internet. “Meanwhile codex couldn't find anything, refused to explain itself and flagged my chat for cybersecurity risk,” they wrote. That post passed a million views.
Why they trusted it
In replies they said .env was listed in their .gitignore, that they'd deployed with Codex many times, and that it had never uploaded the file before: “like 0.001% event i had done this thousands of times.” They also said they can't trust Codex anymore.
Not everyone bought the framing. One well-known developer replied in four words: “You published your .env to cloudflare.” That's the other reading of the same events, and from the outside there's no way to tell which is right.
How it ended
Asked in replies whether they'd have to pay, the developer answered “they refunded” and, to another follow-up, “resolved already”. They didn't say who refunded what, so treat that as their account too.
Our take
Whoever pressed the button, the failure is the same: a secrets file ended up in a public deploy. A .gitignore file tells git what to skip. Whether a deploy tool honours it depends on the tool and how it's run, so don't lean on it. Deploy a build output folder that never contains secrets, not a whole project folder. Scan what's about to go live for keys before it ships. And put a low budget alert on every cloud key, because $0 expected versus five figures is a gap you want to hear about early.
Never let an agent deploy a whole folder blind. Keep secrets out of build output and scan before you publish.
