{
  "id": "railway-october-ai-key-theft-2026-10",
  "name": "Railway October 2026 incident - build escape to decrypted customer AI provider keys",
  "date_reported": "2026-11-10",
  "researcher": "Jacob Cooper, Angelo Saraceno, Sarah Bedell, Luca Casonato",
  "org": "Railway",
  "sources": [
    {
      "url": "https://blog.railway.com/p/incident-report-october-security-incident",
      "title": "Railway: Incident Report, October 21st Security Attack",
      "publisher": "Railway"
    },
    {
      "url": "https://www.wiz.io/blog/black-october-for-ai-developer-platforms",
      "title": "Wiz: Black October for AI developer platforms",
      "publisher": "Wiz"
    },
    {
      "url": "https://www.bleepingcomputer.com/news/apple/railway-breach-leads-to-740-000-in-fraudulent-ai-charges/",
      "title": "BleepingComputer: Railway breach and fraudulent AI charges",
      "publisher": "BleepingComputer"
    },
    {
      "url": "https://thehackernews.com/2026/11/railway-says-stolen-customer-ai-keys.html",
      "title": "The Hacker News: Railway stolen customer AI keys",
      "publisher": "The Hacker News"
    }
  ],
  "magicsword_coverage": [],
  "borderline": false,
  "borderline_note": null,
  "ai_role": "ai_credential_theft",
  "ai_role_secondary": "attacker_uses_ai_as_operator",
  "ai_role_detail": "The attacker selected and decrypted customer AI provider keys. Railway, citing Wiz, also describes the intrusion itself as a contest against abliterated models and an ARTEX-like harness. That operator-side claim is vendor-asserted.",
  "technique_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 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.",
  "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",
  "regions": [
    "Multiple regions"
  ],
  "attribution_or_cluster": "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.",
  "prevention_angle": "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.",
  "related_magicsword_projects": [],
  "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.",
  "last_reviewed": "2026-11-12",
  "iocs": {
    "domains": [],
    "ips": [],
    "hashes": [],
    "urls": []
  },
  "atlas_techniques": [
    {
      "id": "AML.T0021",
      "rationale": "The attacker created a swarm of dummy Railway accounts starting October 18",
      "source_urls": [
        "https://blog.railway.com/p/incident-report-october-security-incident"
      ]
    },
    {
      "id": "AML.T0055",
      "rationale": "Regexes selected AI provider key names in the variables database before decryption",
      "source_urls": [
        "https://blog.railway.com/p/incident-report-october-security-incident"
      ]
    },
    {
      "id": "AML.T0012",
      "rationale": "A build credential, then a cloud credential from a bad OIDC binding, were reused to move laterally",
      "source_urls": [
        "https://blog.railway.com/p/incident-report-october-security-incident"
      ]
    },
    {
      "id": "AML.T0034",
      "rationale": "Stolen keys ran up about 740,000 dollars in unauthorized model usage",
      "source_urls": [
        "https://blog.railway.com/p/incident-report-october-security-incident"
      ]
    },
    {
      "id": "AML.T0016",
      "rationale": "Railway, citing Wiz, describes an ARTEX-like harness and abliterated models used during the intrusion",
      "source_urls": [
        "https://blog.railway.com/p/incident-report-october-security-incident",
        "https://www.wiz.io/blog/black-october-for-ai-developer-platforms"
      ]
    }
  ],
  "attack_flow": {
    "nodes": [
      {
        "id": "signup",
        "title": "Dummy account swarm",
        "description": "Signups begin October 18, two days before the build escape.",
        "kind": "access",
        "source_urls": [
          "https://blog.railway.com/p/incident-report-october-security-incident"
        ]
      },
      {
        "id": "build-escape",
        "title": "Break out of the build",
        "description": "At 07:28 UTC on October 20 a build bug yields a credential that Temporal trusts. 353 build histories are read.",
        "kind": "execution",
        "source_urls": [
          "https://blog.railway.com/p/incident-report-october-security-incident"
        ]
      },
      {
        "id": "oidc",
        "title": "OIDC misbinding to a long-lived credential",
        "description": "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.",
        "kind": "execution",
        "source_urls": [
          "https://blog.railway.com/p/incident-report-october-security-incident"
        ]
      },
      {
        "id": "decrypt",
        "title": "Decrypt AI provider keys",
        "description": "Regex selection and KMS decrypt in two windows on October 21 expose variables for at most 1.85 percent of workspaces.",
        "kind": "ai",
        "source_urls": [
          "https://blog.railway.com/p/incident-report-october-security-incident"
        ]
      },
      {
        "id": "resale",
        "title": "Stolen usage",
        "description": "Keys show up in coding-agent traffic and training-data collection. Unauthorized spend is about 740,000 dollars.",
        "kind": "impact",
        "source_urls": [
          "https://blog.railway.com/p/incident-report-october-security-incident"
        ]
      }
    ],
    "edges": [
      {
        "source": "signup",
        "target": "build-escape"
      },
      {
        "source": "build-escape",
        "target": "oidc"
      },
      {
        "source": "oidc",
        "target": "decrypt"
      },
      {
        "source": "decrypt",
        "target": "resale"
      }
    ]
  },
  "category": "attacks-on-ai",
  "attribution": {
    "actor_name": "Unnamed",
    "country": "Unknown",
    "motivation": "financially-motivated",
    "attributed_by": "Railway; the agent-harness detail is from Wiz as cited by Railway",
    "confidence": "medium"
  },
  "ai_involvement_confidence": "confirmed",
  "detections": [
    {
      "name": "Railway build-escape and KMS decrypt hunting",
      "format": "guidance",
      "notes": "No indexed Sigma, Splunk, or Elastic rule matches Railway's private Temporal client, the build-isolation escape, or application-database KMS decrypts of customer variables. AWS rules for PutKeyPolicy, key deletion, or Kubernetes AssumeRoleWithWebIdentity describe different events and are not cited. On a platform like Railway, alert on a build identity reading job histories, on regex scans of variable names, and on decrypt bursts between new credentials and AI-provider key prefixes."
    }
  ],
  "timeline": {
    "first_seen": "2026-10-18",
    "last_updated": "2026-11-10",
    "updates": [
      {
        "date": "2026-10-18",
        "source": "Railway",
        "summary": "Attacker begins creating dummy Railway accounts"
      },
      {
        "date": "2026-10-20",
        "source": "Railway",
        "summary": "07:28 UTC build escape. 13:50-15:30 UTC the attacker reads 353 build histories, sealed variables included."
      },
      {
        "date": "2026-10-21",
        "source": "Railway",
        "summary": "03:26 UTC OIDC misbinding. 04:42-05:14 and 06:36-07:15 UTC KMS decrypt of AI provider keys. 09:25 UTC revocation requests to GitHub, GitLab, Anthropic, OpenAI, OpenRouter, SpaceXSI, Google, and Stripe."
      },
      {
        "date": "2026-11-10",
        "source": "Railway",
        "summary": "Full incident report. Unauthorized spend estimated at about 740,000 dollars. Wiz harness detail included."
      }
    ]
  }
}