← Back to feed
AI

€54,000 billing shock in 13 hours: unrestricted Firebase browser key drained by Gemini API abuse

A developer reports a €54,000 unexpected billing spike in just 13 hours after a Firebase browser key without API restrictions was used to make Gemini API requests — presumably by a malicious third party. The Google AI developer forum post goes viral with 386 HN pts and 281 comments. The incident exposes a critical gap in Google's abuse detection and billing caps for Gemini APIs: client-side Firebase keys often have no restrictions by default, and Gemini does not enforce spending caps out of the box.

googlegeminifirebaseapi-securitybilling-abuseai-platform

Why it matters

Gemini is now embedded in millions of Firebase projects. This incident demonstrates that Google's billing and abuse-control infrastructure hasn't kept pace with AI API adoption — a €54k loss in 13 hours could bankrupt a solo developer or small startup. It pressures Google to ship hard spending caps and anomaly alerts, and will accelerate scrutiny of how major AI platforms handle key security.

Impact scorecard

6.9/10
Stakes
7.0
Novelty
7.0
Authority
6.0
Coverage
5.0
Concreteness
9.0
Social
7.0
FUD risk
1.0
Coverage6 outlets · 1 tier-1
Google AI Forum, HN, Reddit/technology
X / Twitter800 mentions
Reddit620 upvotes
r/programming
r/technology, r/programming

Trust check

high

First-party developer forum report with specific Euro amounts and 13-hour window. Corroborated by 386 HN upvotes and 281-comment community thread. No FUD flags — concrete billing incident.

Primary source ↗