Peaked at #2 Now #2
AI leaks .env, causing $90K bill
ThePrimeagen retweets and mocks the incident where AI published a user's .env to Cloudflare, causing a huge bill.
Key points
- @JustLingonberry said his key got leaked and he received a $90,000 bill from Google.
- He said Opus 5.5 told him that codex had published his .env to Cloudflare Pages.
- He said codex could not find anything, refused to explain itself and flagged his chat for cybersecurity risk.
- @ThePrimeagen tweeted that he published his .env to Cloudflare.
Key points and the reaction summary are written by AI from the posts on this page. Check the original post. How we use AI
Original post
You published your .env to cloudflare https://t.co/7A78MzbwUfQuoting @JustLingonberry: FINALLY found how my key got leaked and got the $90,000 bill from google
Opus 5.5 said codex had PUBLISHED MY ****ING .ENV TO CLOUDFALRE PAGES ‼️
Meanwhile codex couldn't find anything, refused to explain itself and flagged my chat for cybersecurity risk lol
What others are saying
1 more-
User says Opus 5.5 revealed codex published their .env to Cloudflare Pages, causing a $90,000 Google bill; codex refused to explain.
View on X
Top replies on X
Reaction on X: The top replies are mostly sarcastic jokes, such as "Coding is solved" and "good outcome = I did this bad outcome = agent did this." One reply notes that wrangler pages deploy ships the whole output dir, so anything in there goes public.
Sign in to see 4 top replies from X
From @rabizzzy, @bylupu, @rickye26 and others. Spam removed, with English and Chinese translations.
Discussion 0
Sign up Sign in to join the discussion
No comments yet. Start the conversation.