Security News incident-response authentication ci-cd
SEC News Critical

Railway breach exposes credentials and drives $740,000 in unauthorized AI usage

Attackers escaped filesystem isolation in Railway's build infrastructure, and stolen credentials were used for about $740,000 in unauthorized AI usage, according to BleepingComputer.

KT Kusal Tharindu

Railway, a platform for deploying and running applications, reported a security incident from a large-scale malicious attack that began on October 20, 2026. The company says attackers exploited a previously unknown vulnerability in its build infrastructure to partially escape filesystem isolation.

According to BleepingComputer, at most 1.85% of workspaces, about 100,000, could have had environment variables decrypted. The report says the stolen credentials were subsequently used to generate approximately $740,000 in unauthorized AI usage. The breach also exposed linked-account tokens belonging to 1,852 users, including GitHub OAuth tokens and AI agent keys.

What else the attack reached

The report describes a second step: attackers exploited an improperly configured trust relationship involving OpenID Connect (OIDC — a token-based identity standard) to gain further access to Railway’s infrastructure. Railway’s own account says the attacker read stored histories of 353 builds. Railway halted builds and restored builds for all plans by October 22, 2026.

Why it matters

Linked-account tokens connect Railway to other services, so the exposure reaches credentials that authorize those linked accounts. According to BleepingComputer, the attackers were fully removed from Railway’s systems on October 21, and all exploited vulnerabilities have since been remediated. According to the report, Railway found no evidence that the hackers downloaded customer Git repositories or accessed customer databases.

What to do

Railway recommends that all customers who signed up prior to October 21 rotate their keys stored on Railway. Railway rotated internal credentials and invalidated every user session and token at 20:19 UTC on October 21.

Sources

  1. Incident Report: October 21st Security Attack | Railway Blog
  2. Preliminary Report: Oct 21st Security Incident | Railway Blog
  3. BleepingComputer: Railway breach leads to $740,000 in fraudulent AI charges
3 posts

Discussion

Spotted an error? Send corrections to [email protected] .

Search Oxelan Signal

Type to search the archive.

Search by title, tag, summary or body text.