What happened
Railway's final incident report, published 2026-11-10, says the attacker began probing its build infrastructure at 06:50 UTC on 2026-10-20 and at 07:28 UTC exploited a previously unknown flaw to partially escape filesystem isolation, exposing a build-server credential. A second entry point came from an erroneous OIDC binding in a cloud environment, through which the attacker obtained a short-lived cloud credential at 03:26 UTC on 2026-10-21. Forensics found the attacker's first dummy-account signups on 2026-10-18; Railway says those early attempts failed.3
Between 04:07 and 07:15 UTC on 2026-10-21, the attacker queried the variables database for encrypted envelopes and decrypted some of them using a long-lived key found on an orchestration machine. The stored histories of 353 builds were also read on 2026-10-20. The preliminary report of 2026-10-22 gave somewhat different times for these steps; the final report supersedes it.1,3
Who is affected
Railway says a subset of customer environment variables was decrypted for at most 1.85% of workspaces, about 100,000, and calls that an upper bound because its logs identify environments rather than individual variables. In the preliminary report it said it was also contacting users it judged at high risk of targeting, a group larger than the 1.85%. Railway says it has about 5 million existing users.1,3
Linked-account tokens, including bring-your-own-key agent keys and GitHub OAuth tokens, were decrypted for 1,852 users and reset. The attacker obtained a copy of Railway's internal monorepo through build cache snapshots; Railway says there is no indication customer repositories were downloaded and that it found no logins to Railway accounts using stolen credentials.3
Who is behind it
Railway has not named the attacker. It assesses that the primary target was AI provider credentials, passed to resale operations for model distillation, and says it has not established whether the operator supplied credentials to others. Wiz places Railway in a run of October and November 2026 incidents at AI developer platforms, including Fireworks AI, OpenCode, Warp and Northflank, and describes two key-resale operations it could not definitively link to the attacks.3,4
Financial and operational impact
Railway estimates about $740,000 in unauthorized spend on compromised AI provider keys. Its preliminary report said it could not refund customers for that spend. The final report says AWS Bedrock and Google Gemini are initiating refunds, other providers are reviewing case by case, and Railway will cover losses from providers that do not refund. Wiz notes an unverified social media report linking about $371,000 in cryptocurrency theft to keys stored on Railway; Railway has not confirmed it.1,3,4
Operationally, builds were halted, all user sessions and tokens were invalidated on 2026-10-21, and customers who signed up before that date were told to rotate secrets stored on Railway. New signups were paused from 2026-10-22 and reopened on 2026-11-02, when Railway said free trial deployments remained temporarily unavailable and new customers must subscribe to a Hobby or Pro plan before deploying.1,2,3
Response and recovery
The final report says the attacker was fully evicted at 09:24 UTC on 2026-10-21 and that AI providers were sent lists of potentially exposed keys at 09:25 UTC. The preliminary report had dated confirmation that the attacker no longer had access to 03:32 UTC on 2026-10-22. Builds were restored by tier on 2026-10-22, from Enterprise at 03:32 UTC to Free and Trial at 22:49 UTC.1,3
Railway says it rotated credentials and certificate authorities, rebuilt internal tooling from validated source, moved builds to dedicated ephemeral VMs, restricted and audit-logged secret decryption, and filed a complaint with the FBI's IC3. The recovery incident on its status page was marked resolved at 19:19 UTC on 2026-11-02.2,3
What investors and lenders should watch
For companies that deploy on shared platforms, the exposure sits in the secrets they store there: AI, payment, database and registry keys. Railway's reversal from no refunds to covering unrecovered losses is a direct cost to the platform. Wiz's list suggests the same pattern hit other developer platforms in the same weeks, so counterparties should ask any platform holding their keys how secrets are decrypted and logged.1,3,4
What is not known
- The exact set of decrypted variables is unknown; 1.85% of workspaces is an upper bound.
- The attacker has not been identified.
- Total refunds by AI providers have not been reported.
- The reported cryptocurrency theft linked to Railway-stored keys is unverified.
Timeline
Attacker's first dummy-account signups, which Railway says failed.3
Probing from 06:50 UTC; isolation escape at 07:28 UTC; on-call paged at 13:58 UTC; builds halted at 17:03 UTC.3
Variables queried and some decrypted from 04:07 UTC; attacker evicted 09:24 UTC; providers notified 09:25 UTC; all sessions invalidated 20:19 UTC.3
Preliminary report published; builds restored by tier; signups paused.1,3
Addendum: services fully restored for existing users.1
Signups reopen; free trial deployments still unavailable; recovery incident resolved.2
Final incident report published.3
Video and further coverage
Reading video and press coverage...
Sources
- 1.Preliminary Report: Oct 21st Security IncidentRailway, 2026-10-22 · primary
- 2.Railway Recovery after October 21 Incident (status incident O1VGXWU5)Railway, 2026-11-02 · primary
- 3.Incident Report: October Security IncidentRailway, 2026-11-10 · primary
- 4.Black October for AI Developer PlatformsWiz, 2026-10-30 · research
DFX Cyber Desk, "Railway attacker decrypted customer secrets in up to 100,000 workspaces, hunting AI keys," DFX Intelligence, published 2026-11-19, https://dfxintel.com/cyber/reports/railway
DFX Cyber Desk reports state only what the cited sources say. A ransomware group's claim is reported as a claim, losses are reported only as a source states them, and nothing is attributed without a named source. Methodology