Loading story…
A small three-person software team reported that a stolen Google Cloud/Gemini API key was abused to run up $82,314.44 in charges in roughly 48 hours, a ~455x spike from their typical $180/month spend. The attacker(s) allegedly hammered the Gemini 3 Pro Image and Gemini 3 Pro Text endpoints, and the victim stated they deleted the compromised key, disabled Gemini APIs, rotated credentials, enabled 2FA, and tightened IAM controls while opening a support case.
Both reports indicate Google support initially pointed to the cloud Shared Responsibility Model, signaling the customer may remain liable for charges tied to compromised credentials. The incident was framed as a cautionary example of how exposed or poorly-scoped API keys can become high-impact AI credentials; one report cited research indicating thousands of legacy Google API keys have been found exposed on public websites and warned that default or “Unrestricted” API key settings can enable catastrophic cost exposure unless organizations implement guardrails such as billing budgets/caps, API key restrictions (API/IP/referrer scoping), and tighter quota limits.
Mallory correlates global threat intelligence with your attack surface — know if you’re exposed before adversaries strike.
5 events from the most recent confirmed update back to the earliest known activity.
Developer Charles Jones said his Google Cloud account was hijacked over June 7-8, 2026, resulting in $11,089.77 in unauthorized charges largely tied to Gemini image-generation usage. Google reportedly linked the abuse to a compromised firebase-adminsdk service account key and suspended the account for activity consistent with hijacked resources.
The affected user reported filing a cybercrime complaint with the FBI and planned to provide logs as evidence of credential theft and API abuse. The filing was part of an effort to support the dispute and seek possible goodwill credits from Google.
Following the incident, the team contacted Google Cloud support to dispute the charges and seek relief. According to the reports, initial feedback indicated the charges would likely stand under Google's shared responsibility model.
After discovering the unauthorized usage, the affected developers deleted the compromised key, disabled Gemini APIs, rotated credentials, enabled 2FA, and tightened IAM controls. These actions were taken to stop further abuse and secure the Google Cloud environment.
Between 2026-02-11 and 2026-02-12, attackers used a stolen Google Cloud/Gemini API key to make large volumes of Gemini 3 Pro Image and Gemini 3 Pro Text requests. The abuse drove charges to $82,314.44, far above the victim team's usual monthly spend of about $180.
Vulnerabilities, threat actors, malware, products, organizations, and breaches Mallory has linked to this story.
3 references tracked. Mallory keeps watching after this page renders.
theregister.com
Open sourcecybersecuritynews.com
Open sourcetomshardware.com
Open sourceMap indicators from this story to your assets and identify affected systems in minutes.
Every observed campaign, victim, and pivot linked to actors named in this story.
Malware, exploits, and IOCs connected to the activity described here.
YARA, Sigma, and Snort rules deployed to your SIEM as soon as they’re published.
Get matching new stories delivered to your team as they break — not the next morning.
Ask questions about this story and take action on the answers.
Other stories Mallory is tracking that overlap on entities, sources, or topic labels.
Security researchers reported that **previously “non-secret” Google Cloud API keys** (commonly embedded in public client-side code for services like *Google Maps*, YouTube embeds, Firebase, and analytics) can **silently become usable credentials for Gemini (Generative Language API) endpoints** once the Gemini API is enabled in the same Google Cloud project. Truffle Security described this as a **privilege escalation/incorrect privilege assignment** scenario where long-exposed `AIza...` keys—originally treated as project identifiers for billing and API access control—can unexpectedly grant access to **Gemini-related data and capabilities**, including access to private AI resources (e.g., uploaded files/cached context) and **billable inference usage**, without clear developer warning or explicit re-authorization. Truffle Security’s internet-scale scanning (including Common Crawl) identified **~2,800–3,000 exposed keys** across organizations in multiple sectors (and reportedly even from Google), highlighting the practical risk of key harvesting from page source and subsequent abuse. The primary impact described is **data exposure via Gemini API access** and **cost/abuse risk** (attackers potentially generating significant charges by making API calls). Separate from the API-key issue, Google also announced a **Gemini feature update for Google Workspace** that allows Gemini to search Google Chat history (noted as *off by default*), which is a product capability announcement rather than a vulnerability disclosure.
Jun 29, 2026
Aikido Security reported that standard Google Cloud API keys can continue authenticating for **up to 23 minutes after deletion**, with a median revocation delay of about 16 minutes across 10 tests. The researchers said the gap appears tied to Google’s eventually consistent backend infrastructure, producing inconsistent, region-dependent results in which repeated requests may still reach servers that accept a supposedly deleted key. The behavior was observed not only for **Gemini** access but also for other Google Cloud APIs including **BigQuery** and **Maps**, contradicting Google Cloud interface messaging that deleted keys can no longer be used immediately. Researchers warned that the post-deletion window could let attackers keep using leaked keys to access enabled services, exfiltrate uploaded files or cached Gemini conversation context, and generate substantial cloud charges, especially where automatic billing tier upgrades raise spending caps during spikes. Aikido said newer Gemini-specific API keys revoked in about a minute and service account keys in roughly five seconds, indicating faster revocation is technically feasible, but Google reportedly classified the delayed revocation as intended behavior and closed the disclosure as **"won't fix."** The firm advised defenders to treat API key deletion as a **30-minute incident-response process** and closely monitor usage after revocation.
Jun 29, 2026
Attackers are stealing AI platform API keys and using them to consume paid model services on victims’ accounts, a practice Unit 42 describes as **AI token jacking**. The activity has generated nearly **$1 million in fraudulent charges** before some victims detected the abuse, with malicious infrastructure in some cases driving **tens of millions of API calls per day**. Stolen credentials are being monetized directly and also funneled through gray-market **"transfer stations"** that resell access to legitimate AI services using compromised or discounted accounts. The stolen keys are being obtained through **phishing**, **infostealer malware**, exposed file shares, public code repositories, and poisoned software packages, including self-propagating `npm` packages that can steal credentials and taint later releases. Defenders are being urged to revoke exposed keys immediately, monitor billing and usage for anomalies, enforce spending caps and short-lived tokens, tighten privileged-account controls, restrict network access, and strengthen software supply-chain hygiene; reporting also points to indicators of compromise such as suspicious user-agent strings, malicious IP addresses, and domains linked to transfer-station infrastructure.
Aug 19, 2026