Exposed Google API Keys Could Access Gemini Data and Incur Charges

· Original article ↗

Summary

TruffleSecurity found more than 2,800 live Google API keys exposed in public code that could authenticate to Gemini. Google says it has blocked leaked keys from Gemini and added scoped keys and leak detection.

Key points

  • TruffleSecurity found more than 2,800 live exposed Google API keys in the November 2025 Common Crawl dataset.
  • Keys embedded in public client-side code could authenticate to the Gemini API, potentially allowing access to private data.
  • Researchers said attackers could use exposed keys to make costly Gemini API calls; the researchers estimated charges could reach thousands of dollars per day per account.
  • Google classified the issue as a single-service privilege escalation and said it worked with researchers to address it.
  • Google says new AI Studio keys will default to Gemini-only scope, leaked keys will be blocked from Gemini, and leak notifications will be sent.
  • Developers should check whether Gemini is enabled, audit and rotate exposed keys, and use tools such as TruffleHog to detect leaks.

Article Details

Event Type
Exposure of client-side Google API keys that can authenticate to the Gemini API
Impact
TruffleSecurity reported finding more than 2,800 live exposed keys in the November 2025 Common Crawl dataset. Researchers said copied keys could allow access to private data through Gemini and potentially incur API charges; they estimated that charges could reach thousands of dollars per day for a victim account. The article does not report confirmed exploitation. Google said it had implemented measures to detect and block leaked keys from accessing Gemini.

Vendors

Products

Tools

Industries

Related Articles