Agent Horror Stories

Viewer discretion advised · Updated nightly

← Back to the feed
Curatedcost explosion·

$82,314 in 48 Hours: Stolen Gemini API Key With No Rate Limit

A stolen Gemini API key was used to rack up $82,314 in charges within 48 hours — Google had no rate limiting or spending cap to stop it.

Nightmare Fuel

The key was stolen. The charges were real. $82,314 in 48 hours.

A developer's Gemini API key was compromised, and the attacker immediately began running requests at maximum throughput. Within two days, the bill hit five figures — and it kept climbing. The developer had no way to set a hard spending cap, and Google's platform had no rate limiting that would have caught the anomalous usage pattern.

The charge: $82,314 for two days of API calls they never made. The developer reported the incident to Google, but the damage was done. The API key had been treated as a blank check with no limit.

The incident, reported by The Register, highlighted a systemic problem with AI API billing: stolen credentials with no spending caps create unlimited financial exposure. Traditional cloud services have billing alerts, spending limits, and anomaly detection. Many AI API providers ship with none of these.

Your API key is your credit card number. Except credit cards have fraud limits. Your Gemini API key apparently doesn't.

More nightmares like this