Railway, a cloud platform for building and deploying software that says it has 5 million existing users, says an attacker who broke into its systems in October was able to decrypt environment variables belonging to at most 1.85% of its workspaces, which it puts at about 100,000. The company says the attacker was chiefly hunting for AI provider API keys, and that unauthorised spending on stolen keys was estimated to reach about $740,000.

The figures come from Railway's full incident report, published on its blog on 10 November 2026 and credited to Jacob Cooper, Angelo Saraceno, Sarah Bedell and Luca Casonato. It follows a preliminary report released on 22 October, while recovery was still under way.

“Based on our forensic investigation, we believe the attacker was specifically targeting AI provider credentials, that they could sell to distributed transfer stations for use in distillation.”

Railway, Incident Report: October 21st Security Attack

How the attack unfolded

According to Railway, the attacker began probing its build infrastructure at 06:50 UTC on 20 October. At the time, that infrastructure ran several isolated customer builds on the same virtual machine. At 07:28 UTC the attacker exploited what Railway describes as a previously unknown vulnerability to "partially escape filesystem isolation", reading files on the host and obtaining a credential that build servers use to reach some internal systems.

Railway says its internal Temporal cluster, which drove parts of the build process, accepted that credential as a trusted client. That let the attacker read stored histories of other builds, including some build variables, and retrieve a copy of the company's internal monorepo. Forensics later showed the attacker read the stored histories of 353 builds on 20 October. The build credential was revoked and replaced at 17:28 UTC that evening.

With the source code in hand, the report says, the attacker found "an erroneously defined OIDC binding configuration" in one of Railway's cloud environments. At 03:26 UTC on 21 October they used it to obtain a short-lived cloud credential, then used it to retrieve internal credentials and connect via SSH to an orchestration machine holding a longer-lived credential able to decrypt customer variables.

Railway says database logs show the attacker querying for variable names that matched AI provider keys and prioritising customers with large numbers of variables. Decryption ran from 04:42 UTC until Railway disabled the credential at 07:14 UTC on 21 October. The company says the attacker was fully evicted at 09:24 UTC that day.

“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.”

Railway, Incident Report: October 21st Security Attack

Impact on customers

Railway stresses that the 100,000 figure is a ceiling rather than a count of confirmed victims. "The logs identify a subset of environments, not individual variables, so that figure is an upper bound," the report says. The decrypted data also included linked-account tokens, described as BYOK agent keys and GitHub OAuth tokens, for 1,852 users. Railway says it reset every one of those tokens, notified each user and found no logins to Railway accounts using credentials taken in the incident.

From 09:25 UTC on 21 October, the company asked GitHub, GitLab, Anthropic, OpenAI, OpenRouter, SpaceXSI, Google and Stripe to revoke potentially compromised keys. It says running services stayed online, but builds were halted twice, every user session and token was invalidated at 20:19 UTC on 21 October, and builds for all plans were restored by 22:49 UTC on 22 October.

On the estimated $740,000 in unauthorised spend, Railway says it is working with providers on refunds and will cover the losses itself where a provider will not.

Background

Railway first disclosed the incident on 21 October. Its preliminary report said customers experienced interrupted builds and deployments, as well as periods of dashboard, API, CLI and support unavailability, and recommended that all customers who signed up before 21 October rotate keys stored on the platform.

The full report says Railway had already built a new build system that gives each build its own virtual machine, and had planned to begin rolling it out in the week of 26 October. It brought that rollout forward for all users after the attack. Railway also says it filed a complaint with the FBI's Internet Crime Complaint Center (IC3), is working with a specialist forensics firm whose investigation is ongoing, and will publish indicators of compromise once law enforcement agrees.

The company places the incident in a wider pattern, saying OpenCode, Warp, Fireworks AI and several others disclosed similar thefts between 6 and 23 October.

“This was a novel and sophisticated attack against our infrastructure, one of many against companies in the developer tooling space.”

Railway, Incident Report: October 21st Security Attack

Analysis

In my view, the most useful part of this report is how ordinary each link in the chain was. A partial sandbox escape exposed a build credential; an internal service trusted that credential more widely than intended; and a single misconfigured OIDC binding turned source-code access into cloud access. None of those steps needs to be exotic to be damaging once they line up.

The incident also shows that AI API keys are now a prime target in their own right, because they can be turned into money quickly. If you keep provider keys in any hosting platform's environment variables, it is worth using per-project keys with spending limits and alerts, so that a leak shows up as an alert rather than a large bill. Railway's candour about timelines and its upper-bound figure is welcome, but customers who stored secrets there before 21 October should treat rotation as done only once they have checked usage logs on the provider side too.

About this report

Based on Railway's official incident report of 10 November 2026 and its preliminary report of 22 October 2026, both published on the Railway blog. Facts and quotes are taken from the sources credited below, which I read on 12 November 2026, and checked against the further reporting listed. Sections marked "Analysis" are my own view. I am an independent developer and am not affiliated with the organisations named here.

Credits and sources

Corrections

Spotted an error? Please contact me. Corrections are noted on this page with the date.