Railway, which developers use to build and deploy their services, has told every one of its users to replace the secrets they store on it. In a security disclosure published at 21:44 BST on Wednesday, the company said “an unauthorized third party may have accessed encrypted environment variables and, for some of them, obtained the decrypted contents”. Those variables, it noted, can hold API keys and database and registry credentials.
TSN tracks attacks like this on its ransomware and cyber attacks hub.
Railway said it detected “anomalous activity involving systems that store customer environment variables” earlier that morning. At first it did not say how many customers were affected or how the attacker got in. Its “initial analysis suggests the impact may be limited to a subset of users”, the disclosure says, but the advice applies to everyone: “we strongly recommend that you immediately roll all environment variables, including any API keys, stored in Railway, as well as any private registry credentials, and review logs for those services for unusual activity.” Railway said it would email customers directly once it confirmed which accounts were affected.
Railway links the breach to attacks on AI providers
The most striking line in the disclosure is about motive. “We believe this is part of a series of attacks recently targeting platform companies with the aim of compromising AI inference providers,” Railway wrote, adding that it had notified those upstream providers “to revoke all keys proactively”. It did not name the providers or the other platform companies.
Its follow-up guides, published in the early hours of Thursday, point the same way. Railway has posted step-by-step advice on checking for unexpected Anthropic, Grok and OpenRouter usage, telling customers to look out for bills or rate-limit consumption that rose “without a matching change in your traffic”. The OpenRouter guide warns that a leaked key “spends your prepaid credits directly”. Other guides cover rotating PostgreSQL credentials and redeploying storage buckets.
Railway is not the only platform to report exposed environment variables this week. On Monday, TSN reported that Zeabur said an attacker had read platform env vars and accounts. Railway has not said whether Zeabur is among the companies it had in mind, and there is no public evidence yet that the two incidents are connected. Northflank has since told its users to rotate all secrets after its own incident, and Wiz has grouped these cases into what it calls a ‘Black October’ for AI developer platforms.
Railway’s preliminary report puts the exposure at 1.85% of workspaces
On 22 October Railway published a preliminary incident report that answers some of the open questions. It says the attack ran from 14:58 BST on Tuesday 20 October to 04:32 BST on 22 October, began with a privilege escalation in its build infrastructure, and reached credentials for its CI environment that let the attacker decrypt artefacts holding further API access. Railway then found an unauthorised database query of encrypted environment variables, a subset of which were decrypted.
The report says at most 1.85% of workspaces, about 100,000, had some environment variables potentially compromised. Because the keys were envelope encrypted, Railway says it cannot tell exactly which variables in each affected project were read, so it is contacting confirmed and high-risk customers and recommends that everyone who signed up before 21 October rotate their keys. It says the attacker did not log into user accounts, but it has not yet ruled out access to source code. The attacker’s payload logs showed the API key names it was hunting for, and Railway believes the aim was to obtain AI provider keys for model distillation. It says it asked GitHub, GitLab, Anthropic, OpenAI, OpenRouter, Stripe and others to revoke potentially exposed keys at 10:25 BST on 21 October, hours before its public disclosure.
For customers, the report shifts the risk without removing it. A cap of 1.85% sounds small, but 100,000 workspaces is a large pool of API keys, and envelope encryption means no single customer can be told for certain that their keys were safe. The early alert to AI inference providers was the most useful step for limiting fraudulent spend, yet the report also says Railway cannot refund charges run up on other platforms with stolen keys. Railway says it has moved to single-tenant build environments, rebuilt its internal tooling and rolled every storage bucket credential, and that a final forensic report will follow.
Update, 22 October 2026 (reported crypto theft)
A blockchain investigator has linked the Railway breach to the theft of about $371,000 in cryptocurrency, crypto.news reports. Taylor Monahan’s analysis finds more than 500 transactions draining funds from over 200 addresses across at least 19 Ethereum-compatible networks, using what she assessed as “a relatively standard wallet sweeper script”. She places the first known theft at 20:36 BST on 21 October, before Railway’s public disclosure, and attributes the drains to private keys stored in Railway. The figure is an outside estimate. Railway has not confirmed any cryptocurrency losses or said how wallet keys were obtained, crypto.news notes.
Customers have had to wait to apply new credentials
Rotating secrets is only half the job; services then have to be redeployed to pick up the new values, and for most of the night that was not possible. “All deployments are paused while we investigate,” the disclosure said. Railway’s status page shows the company rotating all storage bucket credentials from 23:10 BST, then, at 05:17 BST on Thursday, invalidating every Railway API token, which means integrations using its public API stopped working until customers create new tokens.
Builds came back first for Enterprise workspaces, at 04:32 BST, with Pro, Hobby, then Free and Trial customers to follow in stages. At 06:20 BST Railway said deployments were taking longer than usual to move through each stage and that it was working on a fix.
The disruption predates the disclosure. Railway’s status page first reported a problem at 08:24 BST on Wednesday, and for much of the day its dashboard, API and support site were partly or wholly unavailable. At 21:19 BST it invalidated users’ login sessions, citing “impact from adjacent cache systems”, which signed some customers out. At the time, Railway did not say whether that outage was caused by the attack. Its later report says it halted builds on purpose during triage and that dashboard, API, CLI and support outages happened while it contained the intrusion; running customer services stayed online throughout.
That leaves customers with an uncomfortable calculation. Railway thinks only some users were hit, but because it cannot say which individual variables were decrypted, any key stored on the platform before 21 October should be treated as possibly in someone else’s hands until it has been rotated.
Update, 31 October 2026: This article has been updated with figures from Railway’s 22 October preliminary report, including the 1.85% workspace cap, the attack timeline and the build infrastructure entry point, and with its explanation of the build and dashboard outages. Railway says a final forensic report will follow.
Sources
- Railway: Security Disclosure: Wednesday October 21st
- Railway: Preliminary Report: Oct 21st Security Incident (22 October 2026, updated 26 October)
- Railway Status
- Railway: Security Disclosure Recommendation: Check for Unexpected Anthropic Usage
- Railway: Security Disclosure Recommendation: Check for Unexpected Grok Usage
- Railway: Security Disclosure Recommendation: Check for Unexpected OpenRouter Usage
- crypto.news (Rony Roy): Railway security breach linked to $371,000 crypto theft across 19 chains (22 October 2026)
Get TSN’s biggest tech stories, explained.
News and insights across AI, tech, crypto and cybersecurity. Every source linked. Unsubscribe anytime.
Get the newsletterRelated stories
- China-Aligned Group Used AI Agents in ConnectWise Hack, Microsoft Says
- Zeabur Says an Attacker Read Platform Env Vars and Accounts
- Northflank Tells Users to Rotate All Secrets After Security Incident
- Wiz Counts Nine AI Developer Platform Breaches in ‘Black October’
Follow @tsnmediahub on X for breaking AI news as it happens.
Follow on X





