Railway breach exposed customer keys, leading to $740,000 in fraudulent AI charges
BREACHRailwayredteam/daily · 4 sources
- Severity
- High
- Sources
- 4
What happened
Railway says attackers exploited previously unknown flaws in its build infrastructure and a misconfigured trust relationship, starting on 20 October, and were evicted on 21 October. They decrypted about 100,000 customer environment variables, at most 1.85% of workspaces, and generated roughly $740,000 in fraudulent AI usage charges. Linked-account tokens for more than 1,850 users, including GitHub and OAuth tokens, were also reset, and Railway advises customers to rotate secrets stored before 21 October.
For IT people · Written by AI from 4 sources · Wrong?
What to do
- Rotate AI provider keys first, then cloud, database and payment credentials.
- Check AI provider bills and usage logs for traffic your team did not generate, and report unauthorised charges to Railway.
- Check GitHub account audit logs and review all app access, and check registry audit logs such as Dockerhub.
Written by AI from the sources, checked against them
Full story timeline · 4 updates
- Tue 10 NovemberRailway Reveals How Hackers Used AI Agents to Steal API Keys and Rack Up $740,000 in ChargesCyber Security News
- Railway breach leads to $740,000 in fraudulent AI chargesBleepingComputer
- Wed 11 NovemberRailway Says Stolen Customer AI Keys Led to $740,000 in Estimated Unauthorized Usage ChargesThe Hacker News
- Thu 12 NovemberHackers stole AI credentials to get $740,000 in free compute; Railway picked up the billCSO Online
Who reported · 4 outlets
Cyber Security NewsBleepingComputerThe Hacker NewsCSO Online