Railway breach
An Oct 20-21 2026 intrusion at cloud platform Railway in which an attacker escaped build isolation, decrypted customer variables and ran up about $740,000 of fraudulent AI charges with stolen AI provider keys.
What happened
Railway, a cloud application platform, says an attacker first exploited a previously unknown flaw in its build infrastructure on Oct 20 2026 at 07:28 UTC, partially escaping filesystem isolation. Using a build credential, the attacker read 353 build histories and a copy of Railway’s internal monorepo. Early on Oct 21 an erroneously defined OIDC binding gave the attacker short-lived cloud credentials, which were used to decrypt customer environment variables, with AI provider API keys as the priority. Railway says the attacker was fully evicted at 09:24 UTC on Oct 21. No CVE has been published for the build flaw.
Impact
Railway puts at most 1.85% of workspaces, about 100,000, in scope. It reset linked-account tokens for 1,852 users and estimates unauthorized AI spend at about $740,000. Railway believes the keys were resold for model distillation and says the attacker’s first signups began on Oct 18. It describes the incident as a contest of agent speed against an AI-assisted attacker.
Response
Railway halted builds on Oct 20 and 21, invalidated sessions and tokens on Oct 21, restored builds on Oct 22, paused signups from Oct 22 to Nov 2 and filed a complaint with the FBI’s IC3. BleepingComputer links the attack to the “Black October” wave of AI developer-platform breaches that Wiz has tracked; Railway has not named an attacker.
Timeline
Every dated event in the wiki that involves Railway breach, newest first.
- Railway breach: report ties stolen keys to ~$740,000 of AI charges
Railway's incident report says an attacker escaped build isolation, used a build credential to copy its source and read build histories, then abused a misconfigured OIDC binding to decrypt customer variables. Up to ~100,000 workspaces (1.85%) are in scope, 1,852 users' linked tokens were reset, and AI provider keys were the main target. BleepingComputer links it to the Black October wave tracked by Wiz; Railway names no attacker.
Connections
Railway breach and everything one link away. Drag to move, scroll to zoom, click a node to open it.Open in the full graph →
What links here
Sources
- Railway, “Incident Report: October 21st Security Attack”, Nov 10 2026
- BleepingComputer, “Railway breach leads to $740,000 in fraudulent AI charges”, Nov 10 2026