![]() |
|
Thousands of Public Google Cloud API Keys Exposed with Gemini Access After API Enabl - Printable Version +- Hack Forums (https://hackforums.net) +-- Forum: General Topics (https://hackforums.net/forumdisplay.php?fid=7) +--- Forum: World (https://hackforums.net/forumdisplay.php?fid=445) +---- Forum: News and Happenings (https://hackforums.net/forumdisplay.php?fid=89) +---- Thread: Thousands of Public Google Cloud API Keys Exposed with Gemini Access After API Enabl (/showthread.php?tid=6321594) |
Thousands of Public Google Cloud API Keys Exposed with Gemini Access After API Enabl - Stanley - Mar 10, 2026 Thousands of Public Google Cloud API Keys Exposed with Gemini Access After API Enabl New research has found that Google Cloud API keys, typically designated as project identifiers for billing purposes, could be abused to authenticate to sensitive Gemini endpoints and access private data. The findings come from Truffle Security, which discovered nearly 3,000 Google API keys (identified by the prefix "AIza") embedded in client-side code to provide Google-related services like https://thehackernews.com/2026/02/thousands-of-public-google-cloud-api.html RE: Thousands of Public Google Cloud API Keys Exposed with Gemini Access After API Enabl - W1NK1LL3RX - Mar 10, 2026 That’s pretty concerning because a lot of teams treat public Google Cloud API keys like they’re harmless, but if they can be abused to hit sensitive Gemini endpoints, that turns a simple exposure into a real security issue. It’s a good reminder that API keys should always be tightly restricted, monitored, and never trusted just because they’re used in client-side code. |