AI provider keys that customers stored on Railway were stolen in its October breach and used for an estimated $740,000 in unauthorized usage, the company says. Railway now says it will pay those charges itself when an AI provider won’t refund them. That reverses its Oct. 26 line that it was “unable to refund customers,” The Hacker News reports.
- The attacker decrypted environment variables in at most 1.85% of workspaces, about 100,000, and its database queries went looking for AI provider keys. Some queries also matched cloud, database and payment credentials.
- Linked-account tokens for 1,852 users were decrypted, BYOK agent keys and GitHub OAuth tokens among them. All of them were reset.
- The attacker read the histories of 353 builds, including the secrets passed into them.
- On refunds: AWS Bedrock and Google Gemini are refunding under their fraud policies. OpenAI is reviewing case by case. Talks with Anthropic are still going, and Railway is covering breached Anthropic keys in the meantime.
My take
Good on Railway for changing course. The bigger lesson is that a pasted API key is a blank check. Put spend caps and alerts on every AI key you have, and rotate anything that has ever lived on a platform that got breached. I wrote how-tos for both, linked below.
God Bless, and Use the Source!
