Tokenta Signal SIGN IN TERMINAL >
2026.11.07 13:37 UTC
● ISSUE 256 · MICROSOFT × ORACLE × AI CLOUD · Reuters report of Bloomberg News (Duke FM syndication)● ISSUE 255 · TERAWULF × Q3 2026 × WULF · TeraWulf Q3 2026 results (GlobeNewswire release)● ISSUE 254 · PSI × QUANTUM · PSI Aaronson-Ambainis proof announcement (PSI)● ISSUE 253 · IBM × QUANTUM · IBM Quantum System Two Chicago unveiling (PR Newswire)● ISSUE 252 · OKLO × Q3 2026 · Oklo Q3 2026 Form 10-Q (SEC)● ISSUE 251 · VISTRA × Q3 2026 × VST · Vistra Q3 2026 results (PR Newswire)
● ISSUE 256 · MICROSOFT × ORACLE × AI CLOUD · Reuters report of Bloomberg News (Duke FM syndication)● ISSUE 255 · TERAWULF × Q3 2026 × WULF · TeraWulf Q3 2026 results (GlobeNewswire release)● ISSUE 254 · PSI × QUANTUM · PSI Aaronson-Ambainis proof announcement (PSI)● ISSUE 253 · IBM × QUANTUM · IBM Quantum System Two Chicago unveiling (PR Newswire)● ISSUE 252 · OKLO × Q3 2026 · Oklo Q3 2026 Form 10-Q (SEC)● ISSUE 251 · VISTRA × Q3 2026 × VST · Vistra Q3 2026 results (PR Newswire)
AI FRONTIER · SIGNAL REPORT

Stolen large-model quota is being resold: Google discloses LLMjacking, with single-day bills above $100,000

A November 2 report from Google Threat Intelligence Group and Mandiant disclosed multiple LLMjacking intrusions in 2026: attackers hijacked companies' large-model access, with fraudulent bills above $100,000 in a single day in individual cases and $1 million cumulatively; the main entry point was leaked cloud identity tokens, with UNC6993 and the LiteLLM vulnerability CVE-2026-40217 among the cases, and stolen quota resold through LLM Mixers such as Jet Night.

ISSUE 177 · 2026-11-02 · SOURCE / Google Cloud Official Blog Report · STATUS / VERIFIED · TOKENTA SIGNAL RESEARCH
GOOGLE × MANDIANT × LLMJACKINGREPORTED + ANALYSIS
IMAGE: Google Cloud Official Blog Report — FROM THE ORIGINAL REPORT ↗
KEY TAKEAWAYS

WHAT HAPPENEDWhat Happened

Google Threat Intelligence Group and Mandiant published the report 'The Rise of LLMJacking' on November 2, disclosing multiple intrusions handled in 2026 in which attackers hijacked companies' access to large models and left the compute bill with the victim. In individual cases, fraudulent bills exceeded $100,000 in a single day, and some organisations ran up $1 million in cumulative bills before cutting off access. Affected organisations were spread across North America, South America and Asia-Pacific, spanning finance, retail, technology and transport.

The main entry point was not the chatbot front end but back-end model resources. The most common initial access was leaked or stolen cloud identity tokens: IAM credentials, service account keys, GitHub personal access tokens and valid session tokens. A group designated UNC6993 entered cloud instances via misconfigured service account keys, obtained large-model API access, and built a fake portal that lured users into pasting JSON payloads containing valid access tokens, bypassing passwords and multifactor authentication. Another intrusion exploited the LiteLLM gateway vulnerability CVE-2026-40217 to elevate an ordinary virtual key into a PROXY_ADMIN master administrator credential.

After access came monetisation at scale. The attackers generated new API keys in bulk and enabled new services, using a 'burn and rotate' method of creating and deleting short-lived service accounts to evade rate limits, while watching the cloud provider's billing console to monitor proceeds. A division of labour has emerged: one side carries out the intrusion, the other operates LLM Mixers that aggregate, meter and resell the stolen quota to underground subscribers.

The emblematic reseller is Jet Night: an unlimited plan at about $60 a month claiming access to frontier models, a tier that at normal market prices should cost $100 to $250 a month. GTIG recorded one attacker using stolen third-party keys to make more than 500,000 large-model API calls in under eight hours in support of Jet Night's service, shifting nearly $1 million in token costs onto victim organisations.

Unlike cryptojacking, which siphons slowly, an LLMjacking bill can spike to its peak within hours. Mandiant's defensive advice is to treat unauthorised enablement of large-model services as a critical security event: in several intrusions, the victim had never enabled the relevant model services at all — the attackers switched them on themselves after obtaining the keys.

WHY IT MATTERSThe bill is the most honest intrusion detector

Traditional intrusion detection watches for malicious code and anomalous logins; LLMjacking is about money. The credentials, tools and gateways the attackers use are all legitimate in form — the only illegitimate part is who the bill belongs to. A $100,000 single-day spike is itself an alarm signal, but only if the company treats its large-model bill as security telemetry rather than a financial statement read at month's end.

This is a direct reminder for every company using large models in the cloud: the exposure of API keys and service account keys is now directly equal to the exposure of the compute budget to theft. Key rotation, least privilege and anomalous-usage alerting — three old chores — carry a new price tag in an era when models are billed by the token.

WHY IT MATTERSAn underground resale market is taking shape

The appearance of services such as Jet Night means stolen quota now has a stable outlet. Attackers no longer need to consume the compute themselves; one intrusion can be sold continuously to subscribers, turning the business model from one-off theft into subscription revenue. That is precisely why GTIG judges LLMjacking will take precedence over traditional resource theft: faster monetisation, higher margins.

The grey zone is trickier. In the same period, Symantec and Carbon Black disclosed another class of relay service that reroutes genuine Codex and Claude Code clients through third-party servers and sells them to markets that cannot use Western AI coding assistants directly. Paying users may not know they are using stolen quota, and the compliance risk spreads from the attackers to end users.

SIGNAL JUDGMENT — ANALYSISThe large-model bill is becoming a new attack surface

Tokenta Signal's judgment: the right way to read this story is to treat API keys as cash. Cryptojacking steals idle compute; LLMjacking steals money priced by the token, and can burn a company's annual AI budget in hours. The defence checklist is short: least-privilege keys, alerts on usage spikes, and treating unauthorised service enablement as a highest-severity event. Checking the logs only after the bill spikes is already $1 million too late.

WHAT REMAINS UNCERTAINWhat Remains Uncertain

The facts in this report are based on the Mandiant and Google Threat Intelligence Group report on the Google Cloud official blog and The Hacker News' November 3 report; both were opened and verified directly, and the core figures and threat-actor designations agree. The single-day figure of more than $100,000 and the cumulative $1 million are case observations from incidents Mandiant handled in 2026, not industry-wide statistics. The assessment that Jet Night operates on stolen keys is GTIG's judgment (it 'believes' so), not a proven conviction. The names of victim organisations have not been disclosed. This report provides a summary and links only and does not reproduce the full report or its images. This does not constitute investment advice.

EVIDENCEEvidence

Screenshot of the primary source page
SCREENSHOT: SOURCE PAGE — cloud.google.com · CLICK TO OPEN THE ORIGINAL ↗

The full report on the Google Cloud official blog and The Hacker News report page were both opened and verified directly; core facts including the single-day figure above $100,000, the cumulative $1 million, UNC6993, CVE-2026-40217, Jet Night's roughly $60 plan and the 500,000 calls agree on both sides.

ORIGINAL: The Rise of LLMJacking: How Threat Actors Monetize Compromised Cloud and Model Resources ↗
cloud.google.com · 2026-11-02 · Google Cloud Official Blog Report

PRIMARY SOURCESPrimary Sources

RELATEDRelated Intelligence

CORRECTIONS: if a fact on this page is wrong, we keep a correction record on the page. Contact team@tokenta.space