Railway: build-infrastructure escalation let attacker decrypt a subset of customer environment variables
Severity: critical · Patch status: patched · Since 2026-10-20
Railway, a cloud deployment platform with about 5 million users, disclosed that an attacker escalated privileges in its build infrastructure from 20 October 2026. The attacker pulled customer environment variables in encrypted form and, using CI credentials it reached, decrypted a subset. Railway estimates that at most about 1.85% of workspaces (about 100,000) had variables potentially compromised. Because it asked upstream providers to revoke all stored keys for all users, the revocation wave is wider than that. Railway says the attacker was hunting AI provider API keys for distillation, that user accounts were not accessed, and that running services stayed online. Builds and deployments were paused, and Railway says the attacker lost access by about 03:32 UTC on 22 October. Source-code access is not yet ruled out, the first-entry method has not been disclosed, and the final forensic report is pending. Separately, on-chain investigator tayvano alleges that about $371,000 was drained from crypto keys stored in Railway; Railway has not confirmed this. Wiz lists Railway among at least nine AI developer platforms with October 2026 incidents.
What to do
- Rotate every secret stored in Railway environment variables (AI provider keys, database credentials, private registry credentials, cloud keys), especially anything created before 2026-10-21, revoking at the issuer first
- If you kept wallet keys or seeds in Railway variables, treat them as exposed and move funds to new addresses. The reported ~$371,000 drain is an unconfirmed social-media claim, and Railway has not confirmed it
- Remove public network access to databases; review GitHub audit logs and installed GitHub App access, and registry (for example Docker Hub) activity logs
- Reconnect GitHub, recreate CLI and CI tokens (all Railway tokens were revoked), and redeploy the latest commit since pushes during the pause were not deployed
- Check AI provider and cloud billing for fraudulent usage; Railway cannot refund spend made with leaked keys, so contact the provider first
Sources
All live incidents on Threat Watch
