So, imagine waking up and checking your email, only to see a Google Cloud billing alert that looks like it belongs to a Fortune 500 company.
You open the console and realize someone is running thousands of Gemini requests through your account. Except it isn’t you. It’s an attacker who found an old API key you forgot about years ago, and they are having a field day on your dime.
This actually happened to me 3 times in the last month. Fortunately my bills were less than $500 but it could have been MUCH WORSE!
THE AIZA PROBLEM
Alright, just to be clear, this is actually happening to real developers right now. Attackers are hunting for older Google Cloud keys—the ones that usually start with AIZA—and using them to call expensive Gemini endpoints.
We’re talking about people getting handed five and six-figure bills for usage they didn't even authorize.
The kicker? Some folks are reporting that Google support is initially refusing to waive the charges. They're leaning on the "shared responsibility" model, which is a fancy way of saying "you left the door unlocked, so the bill is your problem." Not exactly the vibe we want when building with AI.
HOW TO PROTECT YOUR BILLING ACCOUNT
Okay, I don't want anyone in our community staring at a heart-attack-inducing bill. Here is the move:
👉 Go through your old Google Cloud projects and delete any keys you aren't actively using.
👉 Set strict billing alerts and usage quotas so it's literally impossible to run up a massive bill overnight.
👉 Use the Google Cloud API restrictions to make sure your keys can only call the specific services you need.
I put together a full breakdown of what’s happening and how to secure your setup over on the blog.
CHECK OUT THE FULL POST HERE:
So, just out of curiosity... how many "test" projects do you have sitting in your Google Cloud console right now? Might be a good time to do some digital housecleaning!