Railway's 2026 LLMjacking Breach: When PaaS Secrets Become the Attack Surface
In October 2026, Platform-as-a-Service provider Railway disclosed that an unauthorized third party accessed systems storing customer environment variables, potentially obtaining decrypted contents including API keys, database credentials, and private keys. The attacker, identified on-chain as 0xd9773325282874d18cb83f1fe50f14c39750b2ee, drained cryptocurrency wallets whose private keys were stored on Railway before the incident was publicly disclosed. Railway rotated all bucket credentials, invalidated API tokens, and urged customers to rotate all stored secrets. The campaign is assessed to be part of a coordinated series of attacks targeting PaaS platforms to compromise AI inference providers—a technique known as LLMjacking. This incident illustrates the accelerating convergence of cloud credential theft and AI resource abuse. Threat actors are systematically targeting PaaS and cloud environments not merely for data theft but to commandeer AI compute capacity, shift billing costs to victims, and build autonomous offensive AI agents—a trend that fundamentally raises the stakes for any organization hosting AI workloads or secrets in cloud-native environments.
Kill Chain
