Google API Key Flaw Exposes Android Apps to Unauthorized Gemini Access
A structural flaw in Google's API key system automatically grants existing keys access to Gemini AI endpoints, exposing over 500 million Android app installs to data theft and financial abuse.
A flaw in Google's API key system has exposed widely used Android applications to unauthorized access to the Gemini AI platform, allowing attackers to access sensitive data, rack up costs, and disrupt services. CloudSEK disclosed the issue on April 8, reporting that it identified 32 active keys across 22 apps with a combined total of more than 500 million installs.
The vulnerability stems from a design quirk in Google's API key format, originally created for public-facing services like Maps and Firebase. When the Gemini API is enabled in a Google Cloud project, existing keys automatically gain access to AI endpoints without any notification or user consent. This marks a significant departure from earlier guidance, which assured developers that such keys were safe to embed in client-side code.
CloudSEK analyzed 10,000 Android apps using its BeVigil platform and found active keys in 22 applications. In one confirmed case, researchers accessed user-uploaded audio files from an English-learning app via the Gemini Files API. The data included file metadata, timestamps, and accessible links, proving that private content could be retrieved using exposed keys.
"This is a structural flaw," CloudSEK wrote. "Google merged the concept of 'public keys' with server-side AI secrets, and enabling Gemini should have triggered a mandatory key restriction or forced the creation of a new, scoped key."
The risks include access to private files stored in Gemini, unauthorized API usage leading to financial losses, and service disruption through quota exhaustion. Real-world incidents highlight the potential impact: one developer reported $15,400 in charges within hours of a compromised key being exploited, while another organization faced losses of $128,000 despite implementing security controls.
The mobile ecosystem amplifies the threat, as app packages can be easily downloaded and analyzed to extract embedded keys. Many of these keys persist across multiple versions, increasing long-term exposure. Researchers recommend that developers audit their cloud projects, rotate exposed keys, and restrict API access to only the services required.
Infosecurity Magazine has reached out to Google for comment but has not received a response at the time of publication. The discovery underscores a broader pattern where legacy API security assumptions collide with new AI service integrations, creating unintended exposure at massive scale.