Railway breached, customer API keys compromised in $740,000 AI token loss
- Why it's major
- Secrets stored on Railway, a cloud provider, were decrypted, with environment variables of about 100,000 customer workspaces potentially compromised.
- Status
- Closed
- Disclosed
- Updated
- Data exposed
- Encrypted secrets and CI credentials; potentially environment variables of about 100,000 workspaces
- Funds stolen
- At least about $740,000 in AI token spend on customer API keys
- Outage
- Builds, deployments, dashboard, API, CLI, and support, October 20 to 22; new signups paused
TL;DR: Railway, a cloud provider, says a threat actor gained unauthorized access to its internal systems and pulled encrypted customer secrets. About 100,000 workspaces had environment variables potentially exposed, and Railway asked vendors to revoke the keys.
If you use Railway
Railway invalidated user sessions, revoked all Railway access tokens, asked vendors to revoke potentially compromised keys, and covers unauthorized AI spend that providers do not refund. Railway asks customers to:
- Rotate keys and sensitive environment variables stored on Railway before October 21, 2026.
- Remove public network access to databases.
- Check your GitHub account audit logs and review all app access.
- Check audit logs within your registries, such as Dockerhub.
- Redeploy commits pushed while deployments were paused, reconnect GitHub, and recreate CLI and CI credentials.
- Log in using email if your GitHub account email differs from your Railway email.
- Request a refund from your AI provider for unauthorized usage where the provider has a refund process.
- Submit the Railway claim form with the provider, date range, and an invoice or usage report by November 18, 2026.
What happened
Railway, a cloud provider, detected a threat actor who gained unauthorized access to a subset of its internal systems from October 20, 2026 until October 22, 2026 at 03:32 UTC. The threat actor pulled encrypted secrets, accessed credentials for the Railway CI environment, and decrypted a subset of encrypted environment variables obtained through an unauthorized database query. The initial access vector has not been disclosed.
Encrypted secrets of a subset of Railway customers were accessed, and at most 1.85% of all workspaces, about 100,000 workspaces, had environment variables potentially exposed. Customers lost at least about $740,000 in AI tokens through unauthorized usage of AI provider keys stored on Railway. Railway says the threat actor did not access Railway user accounts, and whether the threat actor accessed user source code remains unconfirmed.
Railway halted builds, revoked access to the identified systems, disabled non-essential internal systems, and asked vendors including GitHub, Anthropic, OpenAI, and Stripe to revoke potentially compromised keys. Railway invalidated user sessions, revoked all Railway access tokens, rotated all keys twice, rotated credentials for all storage buckets, and rebuilt infrastructure tooling from validated source. Railway moved builds to single-tenant builder infrastructure, restored the API and deployments for all tiers on October 22, 2026, and later paused new signups.
Timeline
-
N/AIncident resolved for existing users and new signups paused
-
N/AReported by founder of FinHisaab on X
-
N/AAPI and deployments for all tiers restored
Threat actor confirmed to no longer have access to internal systems
-
N/AUser sessions invalidated and all users notified to rotate credentials
Vendors asked to revoke potentially compromised keys and threat actor expelled
N/AThreat actor pulled encrypted secrets and decrypted a subset of environment variables using compromised credentials
-
N/APotential privilege escalation identified in build infrastructure and build pipelines halted
Monitoring detected abnormal system activity and on-call engineering began investigating
Independent analysis you can act on, straight to your inbox.
Thanks. is on the list.
Sources
- Railway blog: Preliminary Report: Oct 21st Security Incident, by Jacob Cooper and Angelo Saraceno (addendum 2026-10-26)blog.railway.com, accessed Oct 22, 2026
- Railway status page: Railway Recovery after October 21 Incident (updates 2026-10-26 to 2026-10-29)status.railway.com, accessed Oct 29, 2026
- Railway on Xx.com, Oct 26, 2026
- Railway on Xx.com, Oct 26, 2026
- @railway_status on Xx.com, Oct 26, 2026
- @railway_status on Xx.com, Oct 26, 2026
- founder of FinHisaab on Xx.com, Oct 25, 2026
- Railway on Xx.com, Nov 12, 2026, 23:43 UTC
- Bulletin: Compensation for unauthorized AI usageblog.railway.com, accessed Nov 12, 2026
- Noah on Xx.com, Nov 13, 2026, 18:31 UTC