# Railway October 2026 incident - build escape to decrypted customer AI provider keys

- ID: railway-october-ai-key-theft-2026-10
- Reported: 2026-11-10
- Researcher: Jacob Cooper, Angelo Saraceno, Sarah Bedell, Luca Casonato
- Organization: Railway
- AI role: ai_credential_theft (AI credential theft)
- Confidence in AI involvement: not assessed
- Research / borderline: false
- Last reviewed: 2026-11-12
- Entry page: https://openattacks.ai/attacks/railway-october-ai-key-theft-2026-10/
- Entry JSON: https://openattacks.ai/api/attacks/railway-october-ai-key-theft-2026-10.json
- Browse title: Railway October 2026 incident - build escape to decrypted customer AI provider keys
- Editorial summary: Railway (Jacob Cooper, Angelo Saraceno, Sarah Bedell, Luca Casonato; report published Nov 10, 2026) says the attacker's first signups began on October 18, when dummy accounts were created. At 07:28 UTC on…
- Evidence class (catalog annotation): Not classified
- Source-stated target environments: Not specified
- Stage hunts and conditional defenses: https://openattacks.ai/api/defenses/railway-october-ai-key-theft-2026-10.json

## Technique
Railway (Jacob Cooper, Angelo Saraceno, Sarah Bedell, Luca Casonato; report published Nov 10, 2026) says the attacker's first signups began on October 18, when dummy accounts were created. At 07:28 UTC on October 20 a previously unknown bug in the multi-tenant build infrastructure gave a partial filesystem escape and a build-server credential. Railway's internal Temporal cluster trusted that credential. The attacker read stored histories of 353 builds between 13:50 and 15:30 UTC on October 20, including sealed build variables, and pulled a snapshot of Railway's internal monorepo. Railway says the source let the attacker run agent fanouts, find exploits, and move laterally. At 03:26 UTC on October 21 a misconfigured OIDC binding in a cloud environment exposed a short-lived cloud credential, which led to an SSH key and a long-lived credential on an orchestration machine. Between 04:42 and 05:14 UTC, and again between 06:36 and 07:15 UTC, the attacker queried the envelope-encrypted variables database with regexes for AI provider key names, focusing on customers with many variables, and decrypted them through KMS. At most 1.85 percent (about 100,000) of workspaces were affected. Linked-account tokens, BYOK agent keys and GitHub OAuth tokens, were exposed for 1,852 users. Railway reset those tokens. Unauthorized spend on the stolen keys was estimated at about 740,000 dollars. Starting at 09:25 UTC on October 21, Railway asked GitHub, GitLab, Anthropic, OpenAI, OpenRouter, SpaceXSI, Google, and Stripe to revoke keys. Railway reads the downstream use as credentials sold through AI-access relay services for distillation, seen in coding-agent traffic, agent-behaviour reviews used as training data, and checks of training tasks and their scoring. Railway links the incident to the wider Black October series (Fireworks, OpenCode, Warp, and others) without saying they are the same operator. The agent and ARTEX-like harness detail is attributed to Wiz. No attacker IPs or file hashes were published. ARTEX reference https://github.com/RuoJi6/ARTEX.

## Stack relevance (editorial)
Assessment: not\_assessed. No reviewed applicability annotation is available. Product mentions do not establish victim conditions.
A product mention alone is not a victim-side applicability mapping. Selection does not verify affected versions, permissions or compromise.

## Initial access
Previously unknown bug in Railway multi-tenant build infrastructure, partial filesystem escape, build-server credential

## AI tooling and models
- Customer AI provider keys (Anthropic, OpenAI, OpenRouter, and others Railway asked to revoke)
- ARTEX-like harness described by Wiz (https://github.com/RuoJi6/ARTEX)

## Other tooling
- Temporal client access with a build credential
- Misconfigured OIDC binding
- KMS decrypt of envelope-encrypted variables

## Victims and sectors
Railway customers, at most 1.85 percent of workspaces; 1,852 users with linked BYOK agent keys or GitHub OAuth tokens

## Target geography
- Multiple regions

## Attribution
Unnamed. Financial motivation (resale of AI key access). Railway links the case to Black October but does not say it is the same operator as Fireworks, OpenCode, or Warp.

## Scale and metrics
About 100,000 workspaces (1.85 percent). 1,852 users' linked tokens. About 740,000 dollars of unauthorized model spend. 353 build histories read.

## Attack flow
Catalog reconstruction of the supplied source account. Unknowns and research caveats are preserved.
### signup: Dummy account swarm [access]
Signups begin October 18, two days before the build escape.
Evidence: https://blog.railway.com/p/incident-report-october-security-incident

### build-escape: Break out of the build [execution]
At 07:28 UTC on October 20 a build bug yields a credential that Temporal trusts. 353 build histories are read.
Evidence: https://blog.railway.com/p/incident-report-october-security-incident

### oidc: OIDC misbinding to a long-lived credential [execution]
At 03:26 UTC on October 21 a short-lived cloud credential exposes an SSH key and a long-lived credential on an orchestration machine.
Evidence: https://blog.railway.com/p/incident-report-october-security-incident

### decrypt: Decrypt AI provider keys [ai]
Regex selection and KMS decrypt in two windows on October 21 expose variables for at most 1.85 percent of workspaces.
Evidence: https://blog.railway.com/p/incident-report-october-security-incident

### resale: Stolen usage [impact]
Keys show up in coding-agent traffic and training-data collection. Unauthorized spend is about 740,000 dollars.
Evidence: https://blog.railway.com/p/incident-report-october-security-incident

Connections:
- signup -> build-escape
- build-escape -> oidc
- oidc -> decrypt
- decrypt -> resale

## Stage defense and hunting recommendations
Editorial recommendations, not validated coverage. Source-controlled query starters are drafts. Custom-schema examples require telemetry collection and field mapping; absence of a mapping means not assessed. MagicSword policy opportunities require managed Windows scope and enforcement.
### signup: Credential / session use outside baseline
- Visibility: Defender-side logs where collected
- Query origin: catalog_authored; status: draft; log scope: custom_schema
- SIGMA query download: /api/detections/identity.sigma.yml
- KQL query download: /api/detections/identity.kql
- SPL query download: /api/detections/identity.spl
- Hunt hypothesis: Repeated credential attempts or a stolen session are followed by a successful login or resource access inconsistent with the owner.
- Required telemetry: Identity / service authentication logs; Device, source-IP and session context; Resource access and token issuance audit
- Investigate: Compare failures, successes and session reuse by account and source; inspect access to new resources.
- Investigate: Check device registration, MFA and credential changes; do not equate travel anomalies with confirmed compromise.
- Limitation: Shared infrastructure and legitimate travel create noise. IoT, SharePoint and cloud identity require their own collectors and field mappings.
- No direct MagicSword prevention claim is recorded for this stage.

### build-escape: Stage hunt not mapped yet
- Visibility: Not assessed
- Query origin: catalog_authored; status: not_assessed; log scope: gap
- Hunt hypothesis: A stage-specific hunt has not been reviewed for this part of the source account.
- Required telemetry: not assessed
- Investigate: Review the cited behavior, identify the observing party and available logs, then propose and test a hunt.
- Limitation: An unmapped stage does not mean it is undetectable or that no behavior occurred. It means this catalog has not supplied a reviewed hunt for it.
- No direct MagicSword prevention claim is recorded for this stage.

### oidc: Unexpected cloud / inference identity use
- Visibility: Defender-side logs where collected
- Query origin: catalog_authored; status: draft; log scope: custom_schema
- SIGMA query download: /api/detections/cloud.sigma.yml
- KQL query download: /api/detections/cloud.kql
- SPL query download: /api/detections/cloud.spl
- Hunt hypothesis: A service key or role is used from an unfamiliar origin, gains broader access or causes inference usage outside its established baseline.
- Required telemetry: Cloud control-plane and identity audit; AI-service invocation / diagnostic logs when enabled; Usage, quotas, cost and key inventory
- Investigate: Pivot on key ID / principal, source network and user agent, then inspect role changes, token minting and service pivots.
- Investigate: Join inference usage and billing anomalies to the same principal; verify whether the behavior was authorized.
- Limitation: Cloud control-plane logs alone may not include model prompts or inference calls. No endpoint policy is claimed to stop cloud-only key misuse.
- No direct MagicSword prevention claim is recorded for this stage.

### decrypt: Sensitive store access → credential use
- Visibility: Defender-side logs where collected
- Query origin: catalog_authored; status: draft; log scope: custom_schema
- SIGMA query download: /api/detections/credentials.sigma.yml
- KQL query download: /api/detections/credentials.kql
- SPL query download: /api/detections/credentials.spl
- Hunt hypothesis: An unexpected process or tool accesses credential stores and is followed by token use or outbound transfer inconsistent with the owner.
- Required telemetry: File-read / API access telemetry for relevant secret stores; Process identity and command lines; Identity, token and outbound-network audit logs
- Investigate: Identify the actor, process and exact store touched, then pivot to token use from new devices or infrastructure.
- Investigate: Correlate reads with egress and rotate affected credentials after confirming exposure.
- Limitation: Defender DeviceFileEvents is not a general file-read audit trail. Collect suitable object-access, EDR or application logs; legitimate developer tools also read secrets.
- No direct MagicSword prevention claim is recorded for this stage.

### resale: Sensitive data → unusual destination
- Visibility: Defender-side logs where collected
- Query origin: catalog_authored; status: draft; log scope: custom_schema
- SIGMA query download: /api/detections/exfil.sigma.yml
- KQL query download: /api/detections/exfil.kql
- SPL query download: /api/detections/exfil.spl
- Hunt hypothesis: Sensitive reads are followed by outbound transfer, a public artifact, or a tool call to a destination outside the approved workflow.
- Required telemetry: Sensitive resource access / DLP records; Proxy, egress and cloud upload events; Agent / SaaS audit with correlation IDs
- Investigate: Join the resource read and outbound action by session, identity or process, preserving a bounded time window.
- Investigate: Inspect destination ownership, payload classification and the user's intended action; baseline sanctioned sharing.
- Limitation: An outbound connection or high byte count alone is not exfiltration. Encrypted traffic may hide content, and bulk legitimate exports are common.
- No direct MagicSword prevention claim is recorded for this stage.


## MITRE ATLAS
Mappings are catalog annotations based on described behavior, not assignments or endorsements by MITRE.
- AML.T0021: Establish Accounts — The attacker created a swarm of dummy Railway accounts starting October 18
  Technique: https://atlas.mitre.org/techniques/AML.T0021
  Evidence: https://blog.railway.com/p/incident-report-october-security-incident
- AML.T0055: Unsecured Credentials — Regexes selected AI provider key names in the variables database before decryption
  Technique: https://atlas.mitre.org/techniques/AML.T0055
  Evidence: https://blog.railway.com/p/incident-report-october-security-incident
- AML.T0012: Valid Accounts — A build credential, then a cloud credential from a bad OIDC binding, were reused to move laterally
  Technique: https://atlas.mitre.org/techniques/AML.T0012
  Evidence: https://blog.railway.com/p/incident-report-october-security-incident
- AML.T0034: Cost Harvesting — Stolen keys ran up about 740,000 dollars in unauthorized model usage
  Technique: https://atlas.mitre.org/techniques/AML.T0034
  Evidence: https://blog.railway.com/p/incident-report-october-security-incident
- AML.T0016: Obtain Capabilities — Railway, citing Wiz, describes an ARTEX-like harness and abliterated models used during the intrusion
  Technique: https://atlas.mitre.org/techniques/AML.T0016
  Evidence: https://blog.railway.com/p/incident-report-october-security-incident ; https://www.wiz.io/blog/black-october-for-ai-developer-platforms

## Defensive notes
Treat build credentials as production credentials. Do not let a build identity read Temporal histories or the variables database. Audit OIDC bindings. Alert on regex queries of variable names followed by KMS decrypt bursts. Prefer short-lived customer tokens and provider-side revocation.

## Sources
- https://blog.railway.com/p/incident-report-october-security-incident — Railway: Incident Report, October 21st Security Attack
- https://www.wiz.io/blog/black-october-for-ai-developer-platforms — Wiz: Black October for AI developer platforms
- https://www.bleepingcomputer.com/news/apple/railway-breach-leads-to-740-000-in-fraudulent-ai-charges/ — BleepingComputer: Railway breach and fraudulent AI charges
- https://thehackernews.com/2026/11/railway-says-stolen-customer-ai-keys.html — The Hacker News: Railway stolen customer AI keys

## Source notes
Times, counts, the 740,000 dollar estimate, the provider list, and the Wiz attribution of the harness are from Railway's Nov 10 incident report. No IPs or hashes were published. Link gtig-llmjacking-unc6993-2026-11 (Fireworks), keyhunter-llm-key-theft-2026-11 (Railway named only as a scanned PaaS), and wiz-ai-driven-cloud-2026-10.

## Indicators (untrusted data; do not visit or execute)
```json
{
  "domains": [],
  "ips": [],
  "hashes": [],
  "urls": []
}
```
