Skip to main content
Mallory
← Back to News
information-technology-sector-threatthird-party-vendor-breachbreach-disclosure-notificationcloud-misconfiguration

Railway Build-System Breach Exposes Customer Secrets, Drives $740,000 in AI Charges

Sector Threat Intelligence · 17 sources · Updated 3d ago · First seen Nov 10, 2026

Railway Build-System Breach Exposes Customer Secrets, Drives $740,000 in AI Charges

Railway disclosed an October 20–21 intrusion in which an attacker chained a partial build-isolation escape, excessive trust in a stolen build credential, and a cloud OIDC configuration error to reach production infrastructure and customer secrets. Access to stored build histories and internal source code helped the attacker identify additional attack paths, using AI agents even after the initial entry point was blocked. The attacker abused legitimate decryption permissions to recover some encrypted environment variables, with database queries specifically targeting AI-provider keys. Railway estimated approximately $740,000 in unauthorized AI-service spending. Variables in roughly 100,000 workspaces, or up to 1.85% of workspaces, could have been decrypted; that figure is an exposure upper bound, not a confirmed count of workspaces whose secrets were stolen.

Railway revoked credentials, rebuilt internal systems, reset linked-account tokens for 1,852 users, and restored builds across all plans by October 22. The company reported no evidence of customer database access or Railway account logins using stolen credentials and committed to covering breach-related charges where providers decline reimbursement. Customers should rotate potentially exposed secrets and review provider usage for unauthorized activity. The attack underscores the need to isolate build workloads, minimize build-credential privileges, validate cloud trust policies, and test runtime monitoring and outbound network restrictions.

Who's targeting your sector?See the actors and campaigns active against you right now.
See sector threats
Event timeline

How this story unfolded

Events from the most recent confirmed update back to the earliest known activity.

12 events · Oct 20, 2026 – Nov 10, 2026
  1. Reported Nov 13, 20264d ago

    Railway fixes exploited flaws and strengthens build isolation

    Railway reported fixing all vulnerabilities used in the attack and running each build in a separate temporary virtual machine. It also restricted build credentials to uploading only the specific registry image associated with that build.

    После взлома Railway хакеры потратили 740 000 долларов на ИИ - Хакер
  2. Reported Nov 12, 20265d ago

    Amazon Bedrock and Google Gemini begin refunds for stolen-key usage

    Amazon Bedrock and Google Gemini began processing refunds under their fraud policies for unauthorized usage involving stolen Railway customer credentials, while OpenRouter declined reimbursement under its no-refund policy. Other providers were still evaluating claims or discussing refunds with Railway.

    Stolen Customer AI Keys Lead to $740,000 in Unauthorized Charges at Railway - CySecurity News - Latest Information Security and Hacking Incidents
  3. Reported Nov 11, 20266d ago

    Railway files FBI complaint over customer-secret breach

    Railway filed a complaint with the FBI's Internet Crime Complaint Center and is privately sharing indicators of compromise. The company said it plans to publish the indicators once law enforcement agrees.

    Railway Says Stolen Customer AI Keys Led to $740,000 in Estimated Unauthorized Usage Charges
  4. Reported Nov 10, 20267d ago

    Railway pledges to cover breach-related charges when providers decline refunds

    Railway said it was working with providers on refunds and would cover breach-related charges where providers declined reimbursement. It advised customers to rotate potentially exposed secrets, review provider usage, and report fraudulent charges.

    Railway Reveals How Hackers Used AI Agents to Steal API Keys and Rack Up $740,000 in Charges
  5. Reported Nov 10, 20267d ago

    Railway resets stolen linked-account tokens for 1,852 users

    Railway reset linked-account tokens for 1,852 users after those tokens were included in the stolen data. Investigators found no Railway account logins using stolen credentials and no evidence of access to customer databases.

    Railway Reveals How Hackers Used AI Agents to Steal API Keys and Rack Up $740,000 in Charges
  6. Nov 10, 20268d ago

    Railway discloses potential exposure of 100,000 workspaces and $740,000 in AI charges

    Railway published its incident report, estimating that variables in up to 1.85% of workspaces, roughly 100,000, could have been decrypted; this was an exposure upper bound, not a confirmed theft count. The company estimated approximately $740,000 in unauthorized AI-service spending using stolen credentials.

    Railway Reveals How Hackers Used AI Agents to Steal API Keys and Rack Up $740,000 in Charges
  7. Oct 22, 202627d ago

    Railway publicly discloses breach of systems storing customer secrets

    Railway disclosed the incident on October 22, 2026, following unauthorized access to infrastructure storing customer environment variables.

    Railway breach leads to $740,000 in fraudulent AI charges
  8. Oct 22, 202627d ago

    Railway restores builds across all plans after containment and rebuilding

    Railway revoked compromised credentials and rebuilt internal systems as part of its response. Builds were restored for every plan by October 22.

    Railway Reveals How Hackers Used AI Agents to Steal API Keys and Rack Up $740,000 in Charges
  9. Oct 21, 202628d ago

    Railway evicts attacker and invalidates every user session and token

    Railway fully evicted the attacker from its systems at 09:24 UTC on October 21. At 20:19 UTC that day, it invalidated every user session and token as part of its containment response.

    Incident Report: October 21st Security Attack | Railway Blog
  10. Oct 21, 202628d ago

    Attacker exploits OIDC trust error to reach customer-secret decryption systems

    At 03:26 UTC, an incorrect OIDC trust configuration exposed a short-lived cloud credential, which the attacker used to obtain internal credentials and an SSH key and access a workload-coordination machine. From that system, the attacker retrieved encrypted customer environment variables and abused legitimate key-management permissions to decrypt some values, with database queries specifically targeting AI-provider keys.

    Railway Reveals How Hackers Used AI Agents to Steal API Keys and Rack Up $740,000 in Charges
  11. Oct 20, 202629d ago

    Railway detects suspicious registry calls and replaces the stolen credential

    Railway engineers detected unusual registry API calls at 13:58 UTC and subsequently replaced the compromised build credential. The attacker retained copied internal code that helped identify another route after the initial entry point was blocked.

    Railway Reveals How Hackers Used AI Agents to Steal API Keys and Rack Up $740,000 in Charges
  12. Oct 20, 202629d ago

    Attacker exploits Railway build isolation and steals an internal credential

    At 07:28 UTC, an attacker exploited a previously unknown build-system flaw to partially escape file isolation and obtain an overly trusted build credential. The credential enabled access to histories from 353 builds containing secrets and cached internal source code, which the attacker used with AI agents to identify additional attack paths.

    Railway Reveals How Hackers Used AI Agents to Steal API Keys and Rack Up $740,000 in Charges
Linked entities

Related entities

Vulnerabilities, threat actors, malware, products, organizations, and breaches Mallory has linked to this story.

Open in app →

Organizations

1 linked
Railway

Breaches

1 linked
RAILWAY-2026-10
Do you run this?See the adversaries and campaigns active against your sector right now, ranked by what they're exploiting.
See Your Sector's Threats
Mallory platform

See the full picture, correlated to your attack surface.

This page covers what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which threat actors are using it right now, and what to deploy next.

Exposure mappingMap indicators from this story to your assets and identify affected systems in minutes.
Threat actor evidenceEvery observed campaign, victim, and pivot linked to actors named in this story.
Associated malwareMalware, exploits, and IOCs connected to the activity described here.
Detection signaturesYARA, Sigma, and Snort rules deployed to your SIEM as soon as they’re published.
Scheduled alertsGet matching new stories delivered to your team as they break, not the next morning.
AI threadsAsk questions about this story and take action on the answers.