Railway tells all customers to rotate secrets after potential breach

Cloud platform Railway said Oct. 21 that an intruder without clearance may have accessed encrypted customer environment variables on its platform and obtained decrypted contents for some of them, and it told users to rotate every stored secret.

Railway’s initial review indicates a limited affected-user group, though the company has not disclosed a specific count and has not said how many users were affected. It disclosed the incident Oct. 21 in a blog post titled Security Disclosure: Wednesday October 21st. It has not disclosed the cause. Jake Cooper, who founded Railway and serves as chief executive, told TechCrunch that a post-mortem on the incident is planned.

Railway runs a cloud platform where developers deploy applications, run APIs, manage databases, and host backend services. Jake Cooper founded Railway in 2020 in San Francisco and serves as chief executive. Railway collected a $100 million Series B investment. BleepingComputer reports that Railway has roughly 4.8 million users and more than 16 million hosted services; OfficeChai reports that Railway serves about two million developers, handles more than 10 million deployments each month, and counts close to one third of Fortune 500 companies among its customers.

Railway paused all deployments while the investigation continues. Railway said builds for Pro and Enterprise workspaces were back by Oct. 22 at 08:44 UTC, though deployments remained delayed with many queued. Hobby, Free and Trial workspaces still had no builds, and recovery was planned in that sequence. Railway notified upstream providers so they could revoke exposed keys ahead of time, changed storage bucket credentials, cancelled Railway API tokens, and ended OAuth sessions and GitHub tokens.

Environment variables may hold private data such as API keys along with database and registry credentials. Possessing customer keys would let attackers sign in and reach data as though they were the real owners.

Railway believes the incident fits a recent wave of attacks targeting platform companies to compromise AI inference providers. Railway described the incident as one of several attacks aimed at AI inference providers, saying those providers were alerted and instructed to revoke all keys. Railway has not named the other platform companies involved or the inference providers.

OpenCode said earlier in the week that intruders took API keys and other credentials from over 1 percent of its customers and blamed an AI distillation attack where numerous agents extract sensitive data from AI models. Railway’s breach is separate from two serious flaws in the PHP programming language disclosed this week.

Railway told all customers to quickly change all environment variables and secrets on the platform, including private registry credentials. Safeguard’s rotation guidance ranks cloud administrator and IAM keys first, followed by database credentials, payment and billing keys, AI inference keys, then source and registry tokens. Railway’s OpenAI guide warns that a leaked key can raise costs without matching traffic changes. Railway also asked customers to review service logs for unusual activity and promised to email users once accounts are confirmed compromised.