‘$15K bill destroyed a solo developer’s startup’: How hackers are using leaked Google API keys to ‘go wild’ with Gemini AI for free
- Exposed Google API keys allow attackers to run unlimited Gemini AI requests
- Developers experience severe financial losses due to unauthorized access to AI infrastructure
- Hardcoded credentials elevate public identifiers into active authentication tokens for Gemini AI
Developers are facing severe consequences as exposed Google API keys are exploited to access Gemini AI without authorization, leading to significant financial losses, experts have warned.
Security researchers from CloudSek found the root cause of these incidents lies in the unintended elevation of publicly available API keys into live Gemini AI credentials.
Many developers have long embedded keys for services like Maps or Firebase in public-facing applications, following Google’s official guidance – never anticipating these keys would gain access to the AI infrastructure.
Article continues below
Elevation of publicly available API keys is the root cause
One case involved a solo developer whose startup nearly collapsed after an attacker used a publicly accessible key to flood Gemini AI with inference requests.
The developer revoked the key within minutes of receiving a billing alert, yet due to a reporting lag in Google Cloud’s billing system, the charges had already reached $15,400.
Similarly, a Japanese company experienced approximately $128,000 in unauthorized Gemini API usage, despite firewall-level IP restrictions.
Also, a small development team in Mexico saw an $82,314 spike in only 48 hours, a dramatic 455-times increase over typical spending.
“This issue does not stem from developer negligence; the implementations were compliant with Google’s prescribed guidelines,” said Tuhin Bose, cybersecurity researcher at CloudSEK.
He explained the architecture effectively converted non-sensitive identifiers into authentication tokens, creating a systemic vulnerability across numerous applications.
CloudSEK’s research identified 32 exposed Google API keys across 22 Android applications with a combined install base exceeding 500 million users.
The affected apps include household names such as OYO Hotel Booking App, Google Pay for Business, Taobao, and ELSA Speak.
Researchers confirmed data exposure in ELSA Speak when they accessed user-submitted audio files via the Gemini Files API.
The vulnerability allows attackers to perform unlimited Gemini API calls, access sensitive user data, and exhaust organizational API quotas.
It can also persist through app update cycles, severely impacting both developers and end users.
Developers who had followed Google’s guidance now unknowingly hold live credentials to powerful AI tools without notification or opt-in prompts.
Technical measures such as revoking keys and restricting project permissions can mitigate exposure.
However, the financial and operational impact on developers is substantial, suggesting that current practices for handling API keys and AI integrations require immediate reevaluation.
Exposure of hardcoded credentials demonstrates the risks inherent in assuming backward compatibility for modern AI-enabled cloud services.
Follow TechRadar on Google News and add us as a preferred source to get our expert news, reviews, and opinion in your feeds. Make sure to click the Follow button!
And of course you can also follow TechRadar on TikTok for news, reviews, unboxings in video form, and get regular updates from us on WhatsApp too.
Exposed Google API keys allow attackers to run unlimited Gemini AI requests Developers experience severe financial losses due to unauthorized access to AI infrastructure Hardcoded credentials elevate public identifiers into active authentication tokens for Gemini AI Developers are facing severe consequences as exposed Google API keys are exploited to access…
