Google API keys may keep working after deletion, giving attackers time to abuse Gemini access and generate costly cloud charges.

A risky revocation gap

Security researchers at Aikido say deleted Google API keys can continue authenticating after users remove them, with the longest observed window reaching 23 minutes. As many developers treat deletion as an emergency brake after sensitive data leaks, this finding demonstrates how simply removing impacted components isn’t always a silver bullet.

Aikido ran 10 trials, sending repeated authentication requests after deleting newly created keys. Some Google systems rejected the credentials quickly, but others kept accepting them until revocation propagated.

Gemini access raises the stakes

The risk extends beyond nuisance traffic, as the research shows a stolen key tied to a project with Gemini enabled could be exploited to access uploaded files, cached context and billable AI services before the key finally stops working.

That delay grows even more dangerous when threat actors automate high-value requests. Even if jus some backend servers still honor the deleted credential, repeated attempts increase the odds of successful abuse.

Billing controls may not stop the damage

The discovery comes amid growing concern over runaway AI bills. Google’s Gemini API billing model employs usage tiers based on payment history, and Google says higher tiers can reach spending caps from $20,000 to $100,000 or more.

Google recently introduced project spend caps and dashboards, but the research suggests response plans should not rely on key deletion alone. Developers should restrict keys by service and client, avoid exposing them in code or URLs, monitor unusual usage and rotate credentials proactively.

Google reportedly declines a fix

Aikido says Google classified the behavior as intended and closed the report as infeasible to fix. The researchers argue the delay is technically solvable, citing faster propagation for other Google credential types and newer Gemini key formats.

Cloud and AI developers should treat leaked Google API keys as active even after deletion. Incident response should include disabling affected services, reviewing activity, checking cached data and contacting billing support immediately.