Railway told customers on October 21 that an intruder reached the systems holding their environment variables and may have walked away with decrypted contents. The variables are where developers park API keys, database logins and registry credentials.
All deployments were paused while the company investigated. Railway also rotated its own storage keys and said it had contacted upstream AI inference providers so they could revoke anything that leaked.
The disclosure named the pattern behind the intrusion. Railway believes the attack belongs to a run of campaigns against platform companies staged to capture access to AI inference providers. In other words, the target was not the hosting bill. It was the tokens that let an attacker spend someone else’s GPU budget.
Railway said early analysis points to a subset of users, but asked everyone to roll every secret regardless. The advice includes private registry credentials and a log review for unusual activity.
Order matters for anyone following it. Secrets tied to AWS, GCP, GitHub or a model provider should be rotated in the upstream service first, then updated in Railway, so the window between the two steps does not leave a live key behind.
Environment variables became a default because they are easy. A platform that decrypts them in order to run containers has to hold the decryption path too, and that path is now the interesting target. The Railway notice is a reminder that convenience-variable storage shifts risk onto whoever runs the store.
