Railway Says Attacker May Have Read Customer Secrets

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. It has not said 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 says it will email customers directly once it confirms 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.

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. Railway has not said whether that outage was caused by the attack, and its updates describe the security work and the build problems side by side without connecting them.

For now, the company’s own wording leaves customers with an uncomfortable calculation. Railway thinks only some users were hit, but until it emails the affected accounts, every key stored on the platform has to be treated as possibly in someone else’s hands.