New report puts Railway breach at as many as 100,000 workspaces

The cloud host Railway told customers on October 22, 2026 to change their secrets after attackers got into systems that keep environment variables. A secret is a key or a code that gives access to a service.

Railway published a new incident report. The attack began on October 20. The attackers got its source code. They also got the decrypted secrets of at most 1.85 percent of its workspaces, about 100,000. Railway says this is the maximum number of workspaces at risk, not the number of confirmed thefts. Railway says it removed the attackers on October 21.

How the attack went

The attackers used an unknown vulnerability in the build system to get an internal credential. They read the source code. They used a second defect in a trust relation to get the keys that decrypt customer secrets. Railway says the fight lasted about 26 hours, and that the attackers used AI agents.

The damage

The attackers searched for AI provider credentials above all. Railway puts the AI use that it did not permit at about $740,000. Tokens of 1,852 linked accounts, such as GitHub OAuth tokens, were also exposed. Railway changed them. It found no sign that attackers got customer Git repositories or databases.

What is not known

The number of workspaces whose secrets were actually stolen is not given. Railway says the attackers wanted to resell the credentials or use them in model distillation. That is its belief. The security firm Wiz links the attack to a wave called “Black October”.

Insight: Stolen AI keys are the target

Earlier reports say attackers tested each stolen key within 30 minutes, and that one key made 1.7 million calls. Railway says the attackers searched for AI credentials first. This reads as a market where a stolen AI key is cash, and the platforms that hold the keys are the target. More attacks on such platforms are possible.