Exposed Google API keys grant attackers free access to Gemini AI, costing developers thousands

Google API keys give attackers unauthorized Gemini AI access

* 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. 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.

Google Bug Leaks Gemini AI Data in Google Pay, Oyo; Millions at Risk

Bad actors can steal user data and trigger unauthorised usage Google's implementation of an application programming interface (API) key architecture has reportedly led to a massive Gemini exposure risk in Android apps. As per the cybersecurity research firm CloudSEK, a particular client-side API key, which previously functioned as an identifier, receives credential privileges after an Android app integrates the Gemini API. This, in the hands of a bad actor, can expose the data users share with the chatbot. Additionally, this can also result in bad actors making unauthorised Gemini API calls, racking up huge bills for the developer. How a Google API Key Triggers Gemini Exposure In a blog post, CloudSEK explained how an API key (AIza...), which was deemed safe by Google to add to the codebase of Android apps, suddenly gains credential privileges after Gemini is integrated into the app. This security flaw builds on the findings of Truffle Security, which found a similar flaw on a Google Cloud project. CloudSEK's BeVigil, a mobile app security search engine, scanned the top 10,000 Android apps (based on number of installs) and found 32 live Google API keys hardcoded in 22 different apps with more than 500 million installs collectively. Some of these apps are Oyo Hotel, Google Pay for Business, Taobao, apna Job Search App, Elsa Speak, HD Sticker & Pack WAStickersApps, The Hindu, ISS Live Now, and more. Interestingly, the report claims that the API key format Alza... is added to the app when a developer wants to embed Maps or Firebase, as per the documentation instructions shared by Google. However, after enabling the Generative Language API, the key gains access to all Gemini endpoints without any warning or notification. So, anyone who decompiles the app can easily gain access to the key, and it acts like a live Gemini credential. For end users, this means any data shared with Gemini, such as documents, images, or audio, and stored in the Files API, can be accessed by the bad actor. Additionally, all sensitive information in the cached AI context can be read, copied, or exfiltrated by the one gaining unauthorised access. Developers and publishers also face significant risks. Gemini API integration is not free. Developers pay for any usage. So, if the bad actor ends up making unauthorised usage, it can rack up massive bills. Additionally, this also puts a regulatory burden on the companies if the users' data is compromised. CloudSEK recommends developers and companies review all API keys in a GCP project, rotate any key that is embedded in a mobile app, restrict keys by service, and not hardcode any API key in the mobile app source code. While end users cannot do much, they should be careful about using Gemini services in an Android app. If they do not trust the app, they should limit their Gemini interaction to the official app and platforms.

Gemini integration bug may put millions of Android users' data at risk: All you should know

Developers risk data breaches and unexpected costs from unauthorised Gemini API usage Ever since AI has seen rapid advancements, data exposure and leaks have become common terms that we hear every day, and it is dangerous. Yet again, a newly surfaced cybersecurity report has flagged potential data exposure risk tied to Google's Gemini integration in Android apps, including some big names, such as OYO Hotel Booking App, Google Pay for Business (50M+ installs), Taobao (50M+ installs), apna Job Search App (50M+ installs), ELSA Speak: AI English Learning (10M+ installs). According to findings by CloudSEK, a commonly used Google API key, which was previously considered safe for client-side use, can gain elevated privileges once the Gemini API is enabled, potentially allowing unauthorised access to sensitive data and services. The issue comes from API keys that developers often embed in the apps for services like Maps or Firebase. While these keys were initially designed to function as identifiers, the report claims that they can inadvertently turn into active credentials after Gemini's Generative Language API is integrated. This means that if a hacker extracts the key by reverse-engineering the app, they could gain access to Gemini endpoints without additional authentication. Also read: Apple iOS 26.4.1 update is here and it fixes a critical iCloud issue The report stated that it analysed 10,000 widely used Android apps and found dozens of exposed API keys across several apps with a combined install base of over 500 million. The report also stated that the vulnerability builds on earlier research by Truffle Security, which pointed to similar risks in the Google Cloud environment. For the users, this can be serious. Data shared with Gemini-powered features, including the files, images and contextual AI interactions, can become accessible if keys are compromised. At the same time, developers can face financial and regulatory risks as the attackers can misuse these keys to make unauthorised API calls. The report also urged developers to audit their API Key usage and avoid embedding sensitive keys directly in app code and apply strict access restrictions.