News for hackers. Stuff that matters.
Re:Google's insecure-by-default API keys and 30h billing lag... by zem on Monday March 30, 2026 @05:22PM (#47579855)
I really hope that one effect of ai code generators making code cheaper to write is that the calculus around "accept vendor lock in return for getting up and running faster" changes dramatically
Re:Google's insecure-by-default API keys and 30h billing lag... by hedora on Monday March 30, 2026 @05:33PM (#47579984)
Is there an easy way to know if I'm vulnerable to this? Like some dashboard page that lists all the API keys with "revoke" buttons?

I did something or another with a google API years ago, and am not looking forward to a random surprise bill. They don't have my credit card, so maybe that'd solve the problem. On the other hand, they could hold a gmail account hostage.

Re:Google's insecure-by-default API keys and 30h billing lag... by drewnick on Monday March 30, 2026 @07:01PM (#47580774)
You should definitely log in to Google Cloud Console and roll all the keys you see in there if you're unsure. I just did the same thing after I realized I had a lot of surface area with these keys.
Re:Google's insecure-by-default API keys and 30h billing lag... by kingstnap on Monday March 30, 2026 @05:39PM (#47580049)
This is interesting but the linked articles is even more interesting.

https://trufflesecurity.com/blog/google-api-keys-werent-secr...

> Even Google themselves had old public API keys, which they thought were non-sensitive, that we could use to access Google’s internal Gemini.

This is just a classic slow clap here for Cloud.

Re:Google's insecure-by-default API keys and 30h billing lag... by ChrisArchitect on Monday March 30, 2026 @05:53PM (#47580182)