cyber.hendryadrian.com
Cyber Attack & Data Breach · thehackernews.com

Railway Says Stolen Customer AI Keys Led to an Estimated $740,000 in Unauthorized Charges

· Original article ↗

Summary

Railway says an October breach exposed customer secrets, including AI provider keys used for an estimated $740,000 in unauthorized spending. The company reports the attacker was removed and the exploited weaknesses closed.

Key points

  • Railway says an attacker exploited a build-system isolation flaw, then used credentials and a misconfigured cloud OIDC binding to access internal systems.
  • The attacker queried encrypted environment variables for AI provider keys and decrypted variables in up to 1.85% of workspaces—about 100,000, an upper-limit estimate.
  • Railway estimates the stolen AI keys led to $740,000 in unauthorized usage charges; the report does not explain the estimate or specify the period covered.
  • The company says decrypted data included linked-account tokens for 1,852 users, which it reset; it found no logins to customer accounts using stolen credentials.
  • The attacker read stored histories from 353 builds and copied Railway's internal monorepo. Railway says its forensics found no customer database access or evidence that customer code repositories were downloaded.
  • Railway says the attacker was removed on October 21, the weaknesses used were closed, and customers should revoke or replace sensitive variables stored before October 21.
  • The attacker has not been identified. Railway says its investigation with a forensics firm continues and that it has filed a complaint with the FBI's IC3.

Article Details

Victim Organization
Railway
Incident Type
Breach initiated by exploitation of a build-system filesystem-isolation flaw, followed by access to internal systems and theft or decryption of customer credentials.
Incident Date
2026-10-20
Disclosure Date
2026-10-22
Data Types Exposed
  • AI provider API keys
  • BYOK agent keys
  • GitHub OAuth tokens
  • Environment variables and build secrets
  • Stored build histories
  • Railway's internal monorepo source code
Affected Records
The company estimated that at most about 100,000 workspaces (1.85%) may have had variables decrypted; this was an upper limit because logs did not identify which variables were exposed. Linked-account tokens were included for 1,852 users, and stored histories of 353 builds were read.
Operational Impact
Stolen AI provider keys were used for an estimated $740,000 in unauthorized usage charges. Railway said it would pay charges when an AI provider would not refund them. The attacker was removed, affected credentials were reset, the exploited weaknesses were closed, and Railway moved users to a new build system. The company reported no evidence that customer databases were accessed or customer code repositories downloaded.
Claim Status
confirmed

Vendors

RailwayAI provider keys that customers stored on Railway were stolen in an October breach and used to commit an estimated $740,000 in unauthorized spending, the platform-as-a-service provider said yesterday. It has promised to

Products

GitHubreport, the decrypted data also included linked-account tokens for 1,852 users: BYOK agent keys and GitHub OAuth tokens. All were reset, each user was notified, and no logins to customer accounts using stolenTemporalThe credential was meant only for build work, but the company's internal Temporal system, which drives parts of the build process, accepted it as a trusted client. Through it, the attacker read some stored histories of

Related Articles