Attackers were inside Railway for one day. The fraudulent AI bill: $740,000.
By Lior AharonovFounder, 7IT Solutions ·
What happened
BleepingComputer reports Railway's 10 November 2026 update: attackers used an unknown build-infrastructure flaw on 20 October, were removed on 21 October, and got credentials used to decrypt customer environment variables. About $740,000 in unauthorized AI usage followed, and at most 1.85% of workspaces (about 100,000) may be affected.
Why it matters
Your environment variables hold API keys for AI providers, and a stolen key turns into an invoice in your name. Railway says the attackers searched for AI provider credentials first, and 1,852 users also had GitHub and AI agent tokens exposed.
What to do
If you deploy on Railway, rotate every secret and AI provider key stored there, check provider usage since 20 October, and set spend caps on each key.

My take
Lior Aharonov
Founder, 7IT Solutions
Your deploy platform is a vault, not a utility. If a key lives in an env var, assume it will be stolen someday, and cap what it can spend.
Sources
| BleepingComputer: Railway breach leads to $740,000 in fraudulent AI charges | bleepingcomputer.com |
Researched with AI tools; every fact is checked against the linked sources.