GTIG / Mandiant: Multi-Cloud LLMJacking and "LLM Mixer" Monetization
Google Threat Intelligence Group and Mandiant reported LLMJacking across several 2026 investigations: actors used other organizations' credentials to run cloud language models at the victims' expense. Some incidents incurred more than US$100,000 in a day. A separate token-routing service handled over 500,000 calls in less than eight hours, passing nearly US$1 million in costs to one victim. The investigations show several routes into cloud or AI gateways and different ways to cash out. For LiteLLM operators, v1.83.14-stable includes the fix for the cited CVE but still lacks the key ownership-change check added in v1.84.0.
Threat Analysis
- Entry points differ between investigations. Mandiant describes cases in North America, South America and Asia-Pacific. Actors used stolen IAM credentials, cloud service-account keys, GitHub personal access tokens (PATs) and model API keys. One actor checked leaked model keys with very small output limits, an indicator such as repeated max_tokens=1 calls rather than proof by itself. Other cases involved an exposed Ollama model service or UNC6993 phishing for an active cloud session. One case combined a stolen GitHub PAT with a suspected web application vulnerability in a containerized cloud environment.
- What investigators observed after entry. Across different engagements, actors discovered models and regional quota, searched repositories and data-warehouse metadata for credentials, and abused cloud service-account token issuance to access secret stores. Some left misleadingly named billing-optimization accounts or added SSH keys. One cloud intrusion used publicly reachable proxies under the D1337-KAIROS persona and deployed a containerized backdoor using the Manus agent framework. The backdoor queried an upstream LLM to reason through instructions and executed the resulting commands locally, supported by SearXNG and a sandbox execution environment. These observations do not supply intermediate steps for the Jet Night case.
- The LiteLLM escalation and its fixes need separate checks. GTIG reports that a follow-on cluster acquired pre-validated Virtual Keys from the initial-access actor and exploited missing authorization for an ownership change through /key/regenerate to obtain PROXY_ADMIN privileges. GTIG cites CVE-2026-40217, a public vulnerability identifier. The maintainer advisory, public CVE record and CISA KEV entry added on November 18, 2026 instead identify a sandbox escape at /guardrails/test_custom_code. Public records establish this mismatch, but do not independently establish the exact vulnerability used in that incident.
LiteLLM v1.84.0 adds the ownership-change authorization check and repairs the Enterprise license-check bypass in key regeneration. An unmodified v1.83.14-stable deployment already includes the cited CVE fix, but still lacks this ownership-change check. Operators therefore need to verify both repairs separately.
- How the stolen capacity becomes revenue. A pay-as-you-go case involved premium inference and service-account churn to bypass rate limits. GTIG describes AWS Bedrock, Google Cloud Vertex AI and Azure OpenAI in the wider activity. The report calls aggregators LLM Mixers because they combine access from multiple sources behind a single resale interface. It associates UNC6993 with new-api and gcli2api, and describes LiteLLM gateways in related investigations. Jet Night used stolen third-party keys to route over 500,000 calls in less than eight hours, at nearly US$1 million cost to one victim. A separate example routed access to newapi.pro.
Applicable AIDEFEND Defenses (9)
getAccessToken), secret-manager bulk reads, and multi-region model activation to detect direct-to-provider LLMJacking and "burn-and-rotate" service-account patterns.max_tokens=1 credential-validation probes across multiple models as well as sudden request-rate surges (500,000+ calls in hours) characteristic of LLM Mixer pooling.What Defenders Should Do Now
- Inventory each provider's allowed identities, regions and model routes. Verify that model calls from unapproved paths fail even with a structurally valid credential. Keep billing and model enrollment permissions separate from ordinary inference.
- Track short credential-validation bursts, abnormal token issuance, new principals and model spending together. Use enforceable quotas where supported and verify actual deny behavior. Budget alerts alone will not stop new usage. Review gateway access logs for anomalous /key/regenerate calls. If the deployment had an Enterprise license and retained LiteLLM audit logs, compare recorded key ownership before and after regeneration. Ordinary access logs may not contain those values; older audit attribution also needs corroboration because callers could override the changed-by field.
- Contain unauthorized access at its issuer, remove confirmed attacker-created principals and runtime workloads, and separately check for persistence and unaccounted usage. For affected LiteLLM gateways, deploy a supported release containing the ownership fix introduced in v1.84.0 and restrict the key management API to independently authenticated management identities.
Conclusion
Last updated: