News · Academy · November 12, 2026

Academy: where your AI API keys should live

Two stolen AI keys ran up more than $100,000 in model calls. Six habits to limit the damage if a platform you use loses your keys.

DRIVE 369 DAO · 3 min read

Academy, organisations, lesson 14. In October 2026 attackers went after a common place teams keep AI keys: environment variables on the platforms that run their code. This lesson is about making a stolen key cheap to lose.

The facts

• Wiz counted at least 16 AI developer platforms that disclosed incidents between October 4 and November 9, and says every public report describes attackers hunting stored environment variables, especially those that grant AI access.
• On Railway, a subset of encrypted environment variables was decrypted, with at most 1.85% of workspaces (about 100,000) potentially affected (Railway).
• Wiz documented two stolen enterprise Amazon Bedrock keys: about 800,000 calls in roughly 30 hours, and about 1.7 million in roughly 13 hours, over $100,000 at list price. The first call came within 30 minutes of the reported theft.

Six habits

1. Know where every key lives. Make a list: key, provider, where stored, who owns it, what it can spend, when rotated. Keys you forgot are the ones nobody revokes.
2. Keep the master copy outside the platform. A platform's environment variables are a convenient copy, not a vault. Keep the original in a manager and paste it where needed. See secrets and rotation.
3. One key per job and per environment. A test key that leaks should not open production. A key for one project should not reach another.
4. Narrowest scope and a spending cap. Restrict the models and actions a key can use, set a budget limit at the provider, and set an alert for unusual volume or unfamiliar models.
5. Watch for the theft pattern. Wiz saw a single validation call shortly after the theft, then 14 to 120 calls a day per key consistent with a verification job, then high volume. A usage alert on the first odd call buys time.
6. Rotate fast, from a clean place. When a platform you use discloses an incident, revoke and reissue every key it stored, starting with those created before the incident. Railway also asks you to review GitHub audit logs and installed GitHub apps, check registry logs, and remove public network access to databases.

If a key leaks

Revoke it first, then look at usage logs for calls you did not make, then contact the provider with timestamps. Do not expect a refund: Railway says it cannot refund spend from compromised keys, though it will help escalate. See the first 24 hours for the order of steps.

How Ghostdrive approaches it

Pass keeps API secrets as sealed items on your device, each with its own key, with the title and website encrypted too, and clears copies from the clipboard after 30 seconds. It is a manager for people and small teams, not a production secrets service, and a key you paste into a platform is that platform's key. Agents connected to Ghostdrive get their own scoped tokens, not your provider keys by default.

Academy: start here · Black October explained · Ten guardrails for agents