Railway says attackers seeking AI provider keys for distillation breached its internal systems
Railway · Incident report
Read the source (opens in a new tab)- What happened
- Cloud host Railway published a preliminary report on October 22, 2026 on an attack from October 20 to October 22 that reached a subset of its internal systems and exposed some customers' encrypted secrets.
- Key points
- Railway says early investigation shows the attack "was attempting to obtain AI provider API keys to perform distillation attacks."
- Initial evidence, it says, suggests the attacker "had access to abliterated models and substantial compute resources which enabled them to perform highly sophisticated exploits against our infrastructure."
- At most 1.85% of workspaces, about 100,000, had environment variables potentially compromised; Railway worked with GitHub, GitLab, Anthropic, OpenAI, OpenRouter, SpaceXSI, Stripe and others to revoke keys.
- Builds, deployments, dashboard, API, CLI and support were interrupted, and Railway recommends that all customers who signed up before October 21 rotate keys stored on the platform.
- Evidence
- The company's own preliminary incident report, written while its forensic investigation continues. It gives no technical detail of the exploits and names no attacker.
- Uncertain
- The AI link rests on Railway's early forensics. It says it cannot yet share the exploits' details and scale, and has not ruled out access to user source code.