About

Hackers Hijack Stolen AI Credentials to Run Costly Workloads on Victims' Cloud Accounts

Published
Score
32

Why it matters

Attackers are stealing AI platform logins and API keys and running their own workloads on victims' accounts. Railway said it absorbed roughly $740,000 in unauthorized AI usage after a breach that may have exposed credentials from up to 100,000 workspaces. Zeabur separately disclosed an August 2026 incident in which attackers obtained project environment variables containing third-party API keys and cloud credentials. Google's Threat Intelligence Group, which is tracking the trend most closely, describes "LLM Mixers," gateways that pool stolen credentials, route requests and resell unauthorized AI access. Sysdig, CrowdStrike, Okta, CloudSEK and Unit 42 have also published findings. The practice, known as LLMjacking, is growing fast. Sysdig recorded a 376% jump in credential theft aimed at AI services between Q4 2025 and Q1 2026, and Google reports average prices for stolen AI accounts more than doubled during 2026.

The scale of the problem is still being measured. The Railway breach has not been fully characterized, and the number of affected workspaces is described as a maximum, not a confirmed count. Google's September 2026 research says AI agents are now automating parts of the credential theft pipeline, but the report does not quantify how much of the activity is automated. CrowdStrike's 2026 Threat Hunting Report counts an 89% rise in AI-related adversary activity from July 2025 to June 2026. Okta found hundreds of unexpired AI-service tokens in a September 2026 infostealer log dump. Google expects attackers to prioritize these targets as legitimate AI demand grows.

Security teams should treat any unauthorized change to an AI account as a critical incident, not a billing anomaly. Audit where API keys and cloud credentials sit in project environment variables, since that is where Zeabur's attackers found them. Google recommends issuing short-lived, narrowly scoped credentials to AI agents rather than long-lived keys. The March 2026 compromise of the LiteLLM gateway library (CVE-2026-33634), which exposed provider credentials across organizations, shows that third-party dependencies in AI tooling are part of the attack surface. Check whether your organization uses LiteLLM and whether those credentials were rotated.

Sources

mail Subscribe to Artificial Intelligence email updates

Primary sources. No fluff. Straight to your inbox.

Also on LawSnap