Railway Breach Exposes 100,000 Workspaces: $740,000 in Stolen AI Keys
Railway says hackers stole AI keys from up to 100,000 workspaces in an October breach, ran up $740,000 in fraudulent charges, and exposed 1,852 users' tokens.
Image: Wikimedia Commons / Joël van der Loo
Cloud hosting platform Railway said on November 10 that hackers stole customer secrets from up to 100,000 workspaces in an October breach and ran up about $740,000 in fraudulent charges on stolen artificial intelligence keys, in a final incident report that sharply raised the scale of the attack.
The attack began at 07:28 UTC on October 20, when an attacker exploited an unknown flaw in Railway's build infrastructure to escape the filesystem isolation that keeps one customer's build apart from another and obtain an internal credential. The attackers then read stored build histories and copied Railway's internal source code. A second flaw in a misconfigured trust relationship yielded the credentials used to decrypt customer environment variables. Engineers fought the attackers for about 26 hours before evicting them on October 21.
Key Takeaways
- Up to 100,000 workspaces could have had decrypted environment variables taken — a maximum, not a confirmed count, Railway stressed.
- Stolen keys generated about $740,000 in unauthorised AI usage. Railway will cover charges that providers decline to refund.
- Linked-account tokens for 1,852 users were exposed, including GitHub OAuth tokens and agent keys. Railway reset them and notified the users.
- No customer databases were accessed and no Git repositories downloaded, Railway said, with no account logins seen using stolen credentials.
How the Railway Breach Happened: Full Timeline From October 20 to November 10
Railway described the intrusion as a running fight rather than a single break-in. "This was not a single breach followed by a single fix. The attacker probed many potential routes, in parallel, with Railway similarly hardening the routes in parallel," the company said in its report. The attackers used AI-powered agents to probe for flaws while engineers worked to close them.
| Date and time (UTC) | What happened |
|---|---|
| Oct 20, 07:28 | Attacker exploits unknown flaw, escapes build isolation |
| Oct 20-21 | Attackers probe routes; Railway hardens systems in parallel |
| Oct 21, 09:24 | Attacker fully evicted after about 26 hours |
| Oct 22 | Railway discloses incident, urges secret rotation |
| Oct 26 | Railway says it cannot refund unauthorised AI spend |
| Nov 10 | Final report: 100,000 workspaces, $740,000 fraud |
What Was Stolen in the Railway Breach and What Customers Should Do
Railway said the attackers' database queries were built to surface AI provider keys in particular, though one query also matched cloud, database and payment credentials. The company believes the stolen credentials were used by services that relay or resell access to AI providers for model distillation. The breach also exposed the stored history of 353 builds, secrets included.
Railway is advising customers to revoke and replace any sensitive variable stored on the platform before October 21 and to rotate keys with the issuing provider, since filing a charge report does not itself revoke a key. Railway is working with affected AI providers on refunds and will absorb charges providers decline to reimburse. The report does not explain how the $740,000 figure was estimated.
It is the latest in a run of breaches hitting technology platforms, after a data breach at Amplifon affected 1.3 million people.
Railway Breach Joins 'Black October' Wave Hitting AI Developer Platforms
Railway linked the attack to a wider wave of intrusions against AI developer platforms that security firm Wiz has called 'Black October'. The campaign has targeted platforms including OpenCode, Warp, Fireworks AI, Northflank and Lightning AI in recent weeks, with stolen AI keys used to run up unauthorised usage.
AI infrastructure stocks have meanwhile drawn heavy investor attention.
Railway said it has filed a complaint with the FBI's Internet Crime Complaint Center and is working with a specialist forensics firm, whose investigation continues. The company has not said when the review will conclude.
Frequently Asked Questions
Was my Railway workspace affected by the breach?
Railway has not named affected workspaces. Customers who stored sensitive variables before October 21 should rotate them, since Railway's logs cannot show which variables were decrypted.
How much did the Railway breach cost in fraudulent AI charges?
About $740,000, according to Railway's final incident report. The company said it will cover charges that AI providers decline to refund.
What should Railway customers do after the breach?
Revoke and replace sensitive variables stored before October 21 and rotate keys with the issuing provider. A charge report alone does not revoke a key.
Is the Railway breach connected to other AI platform attacks?
Railway linked it to a wave of attacks on AI developer platforms that Wiz calls 'Black October', including OpenCode, Warp and Fireworks AI.
