9 AI dev platforms breached in October; rotate your API keys now
A chained campaign pulled AI keys from env vars at Railway, Warp, OpenCode and six more — one stolen key drove 1.7M Bedrock calls billed to its owner.
Copy markdown
Nine platforms, one month, one target
Wiz's 'Black October' tally lists nine breached AI dev platforms — Fireworks AI, Lightning AI, Railway, Warp, OpenCode, Zeabur, CommandCode, Northflank and Andromeda — the newest (Northflank) disclosed Oct 30. The prize wasn't the models but the stored environment variables holding your provider keys.
The six-figure Bedrock bill is yours
In two cases stolen keys fired roughly 800k and 1.7M Amazon Bedrock calls — Wiz estimates $100k+ in list-price usage charged to the victims — and OpenCode users reported surprise bills from hundreds to thousands of dollars. A leaked key is now an instant, metered liability.
Railway: ~100,000 workspaces, keys pre-revoked
Railway says up to ~1.85% of workspaces (about 100,000) had encrypted secrets accessed and a subset decrypted after an attempted privilege escalation in build infra; it proactively pushed keys to OpenAI, Anthropic, GitHub, GitLab, OpenRouter and Stripe for revocation. Attacker access ran Oct 20 13:58 to Oct 22 03:32 UTC.
Rotating isn't just hitting 'regenerate'
Per Railway's recovery guide, revoke at the provider first, then update the platform variable AND redeploy every dependent workload — a changed env var alone leaves running processes on the old key. Inventory prod, staging, preview, workers and cron before you call it done.
No single patch to apply
Entry points span the stack: credential theft (Fireworks, Zeabur, Lightning), build-infra privilege escalation (Railway), a third-party vendor dependency that leaked agent logs (Warp), and distillation-driven key abuse (OpenCode, CommandCode). If you pasted a key into any hosting dashboard this month, treat it as burned.