Live threats
HighMicrosoft FORGE Lab Discovers 33 New Linux Kernel CVEs, Including 8 Privilege‑Escalation Flaws BreachMaersk Confirms Legacy System Breach; Hackers Claim 100 GB Data Theft and $5 M Ransom Demand Rule changeTreasury publishes FY27 Social Impact Partnerships to Pay for Results Act Notice of Funding Opportunity DeadlineFarm Credit Administration amends employee payroll system of records under Privacy Act, effective Nov 24, 2026 CriticalMultiple Critical Vulnerabilities in Mozilla Firefox and ESR Enable Arbitrary Code Execution BreachRailway PaaS Reports Theft of Customer AI API Keys Resulting in $740K Unauthorized Usage Rule changeHHS publishes modifications to NIH system of records under the Privacy Act CriticalSGLang Remote Code Execution Exploit Compromises NEAR AI Inference Server, Exposes Data of ~100 Users and 18 Agents
Updated 07:51 UTC All intelligence →
BREACH WATCH BRIEF High 👤 Breach

Railway PaaS Reports Theft of Customer AI API Keys Resulting in $740K Unauthorized Usage

Railway disclosed that attackers stole API keys stored for AI services and generated $740,000 in unauthorized usage. The breach underscores the need for robust secret‑management and access‑control controls to satisfy audit‑readiness across frameworks.

SeverityHigh
Type👤 Breach
ConfidenceHigh
ReportedNov 11, 2026
Technology & SaaS Technology SaaS platforms that store third‑party API keys Enterprises integrating AI services via shared secret stores Stolen Credentials Credential Compromise

What happened

In October 2026 Railway’s secret‑management subsystem was breached, exposing customer‑supplied AI API keys. Attackers used those keys to generate massive AI request volumes, incurring $740,000 in usage fees before Railway detected the anomaly and began remediation.

Why it matters for trust and compliance

  • The incident tests the control objective of protecting and managing cryptographic secrets, a requirement that maps to multiple frameworks and demonstrates the need for auditable secret‑management processes.
  • Validate that secret‑storage processes enforce least‑privilege access and are continuously monitored.
  • Collect evidence of key rotation and usage‑anomaly alerts to support audit readiness.

Who is affected

Technology SaaS platforms that store third‑party API keys Enterprises integrating AI services via shared secret stores

Recommended actions

  1. Rotate all compromised API keys and adopt short‑lived tokens.
  2. Enable real‑time usage anomaly detection on AI service accounts.
  3. Harden secret‑management controls: encrypt at rest, enforce zero‑trust access, and log all retrieval events.

Regulations library

Every US state privacy law, on one map

24 states have a comprehensive privacy law in the library, alongside the EU, UK, US federal and global laws: 102 in all, each explained in plain words with its sources. Select a state to see what applies there.

  • In force
  • Coming into force
  • Sector laws
AK ME VT NH WA ID MT ND MN IL WI MI NY RI MA OR NV WY SD IA IN OH PA NJ CT CA UT CO NE MO KY WV VA MD DE AZ NM KS AR TN NC SC DC OK LA MS AL GA HI TX FL

Get the Breach Digest

The incidents that matter for your vendors and your data, analyzed for practitioners, in one email.