Vendor incident, severity critical
Railway breach exposed customer environment variables; $740,000 in fraudulent AI charges
Published
Attackers exploited a build infrastructure vulnerability and an improperly configured trust relationship at Railway to obtain internal source code and decrypted customer environment variables for up to about 100,000 workspaces. Stolen AI provider, cloud, database and payment credentials were used to generate roughly $740,000 in unauthorized AI usage. Linked-account tokens for 1,852 users, including GitHub OAuth tokens and AI agent keys, were also exposed.
What's affected
- railwayevery version
Exposure window: to UTC.
What to do
- Rotate all secrets and environment variables stored in Railway workspaces, prioritizing AI provider credentials
- Rotate cloud, database and payment service credentials stored in Railway
- Review AI provider usage and billing for unauthorized charges and contact providers about reimbursement
- Reconnect linked accounts after Railway's token reset and check GitHub OAuth tokens and AI agent keys
Secrets to rotate if you were affected
Environment variables, AI API keys, Cloud credentials, Database credentials, GitHub tokens.
Check whether you were affected
Pharon tells teams automatically when this affects something they run. To check a machine, run this in Claude Code with the Pharon plugin, in the repository that uses it:
/pharon:check-incident railway-breach-2026-11References
Notice railway-breach-2026-11, signed with key feed-prod-2026-10 (Ed25519). The Pharon CLI verifies the signature before using a notice.