AI keys were stolen for $740,000: Railway's final report and the Black October lesson
Direct answer
On November 10, 2026, hosting platform Railway published its final report on the intrusion of October 20 and 21: an attacker broke build isolation, reached a misconfigured OIDC trust relationship and decrypted customer environment variables. The decrypted variables could belong to up to 1.85% of workspaces, about 100,000 as an upper bound. Linked-account tokens for 1,852 users were exposed and were reset. The stolen keys were used to run up about $740,000 in unauthorized AI usage. Railway says it will cover charges that providers decline to refund.
How the attack happened, step by step
- October 20, 07:28 UTC: the attacker exploited an unknown flaw in Railway's build infrastructure and broke filesystem isolation, the separation between one build and the rest of the platform.
- The key hunt: logs show the attacker filtered the encrypted variables database with regular expressions matching AI provider key names. The goal was clear: AI provider API keys to resell and use in model distillation pipelines.
- October 21, 07:14 UTC: Railway took the blunt option: it disabled every active cloud credential, revoked static credentials, turned off the decryption service and shut down parts of the platform.
- October 21, 09:24 UTC: the attacker was fully evicted, about 26 hours after the start. Builds were fully restored on October 22 at 22:49 UTC.
- What was taken: decrypted environment variables from up to 100,000 workspaces, the history of 353 builds and linked tokens for 1,852 users. The customer database was not accessed, and Railway saw no account logins with the stolen credentials.
Black October: Railway was not an isolated case
- One coordinated campaign: security firm Wiz called the run of breaches "Black October": between early October and early November, attackers targeted developer platforms and their main goal was always the same: AI provider API keys.
- The other names on the list: Fireworks AI, OpenCode, Warp, Lightning AI, Northflank and Zeabur reported similar thefts between October 6 and 23. Fireworks AI expanded its bulletin on November 9. Zeabur said it will shut down.
- The pattern is money: a stolen API key becomes free compute for whoever uses it and a bill for its owner. Railway estimates that just two keys generated more than $100,000 in usage at list price, according to Wiz.
- Who pays the $740,000: AWS Bedrock and Google Gemini started fraud refunds; OpenAI and SpaceX review claims case by case; talks with Anthropic are ongoing and Railway is covering those costs meanwhile. OpenRouter keeps its no-refund policy, so Railway says it will pay those bills. Railway filed a complaint with the FBI's IC3 and engaged a forensics firm.
What to do in your business this week
- Rotate keys that touched Railway: if your team used Railway before October 21, change every AI provider key that sat in environment variables. Railway already reset the linked tokens, but your provider keys are yours, and rotation is on you.
- One key per use, with a cap: every agent and every environment deserves its own key, with a spending cap and limited permissions. One master key that does everything is a single door for the attacker.
- Separate secrets from code: provider keys do not belong in environment variables on a shared build platform without proven isolation. Use a secrets manager with audited access and automatic rotation.
- Watch spending in real time: the attack was detected partly through anomalous spending. Set spending alerts per key and per day: a key that suddenly spends ten times more is a compromised key until proven otherwise.
Note: this article summarizes Railway's final report of November 10, 2026 and coverage in BleepingComputer, getaibook, ShiftDelete and Dev.to. The figures of 100,000 workspaces, 1,852 users and $740,000 are from Railway's report; the 100,000 is the estimated upper bound Railway published. The OpenRouter breach claim is a dark-web allegation with no published confirmation from OpenRouter.
Want AI that works for your business?
Message us on WhatsApp and let's talk about automation and AI agents for your business.
WhatsApp inicIARelated articles
- Fireworks AI widened its breach: billing data, datasets and model weights in attackers' hands
- Black October: AI found decade-old PHP flaws and the world rushed to patch
- OpenAI revealed 4 cases of agents crossing limits: the containment checklist for your business
Frequently asked questions
What happened at Railway in October 2026?
An attacker broke build isolation on October 20, decrypted customer environment variables and used stolen AI provider API keys to run up about $740,000 in unauthorized usage. Railway evicted the attacker on October 21 and published its final report on November 10.
How many customers were exposed?
The decrypted variables could belong to up to 1.85% of workspaces, about 100,000 as the estimated upper bound Railway published. Linked tokens for 1,852 users were exposed and were reset.
Who pays the $740,000 in charges?
Railway says it will cover charges that providers decline to refund. AWS Bedrock and Google Gemini started refunds; OpenAI and SpaceX review case by case; talks with Anthropic are ongoing.
What should I do if I used Railway?
Rotate every AI provider key that sat in environment variables before October 21, give each agent its own key with a spending cap, move secrets to a manager with audited access, and set spending alerts per key.
