In a report published on November 2, 2026, Google Threat Intelligence Group and Mandiant describe attackers hijacking and reselling access to AI models. This LLMjacking leaves the organization whose access was compromised paying for consumption. Some investigated incidents exceeded $100,000 in one day, with cumulative charges reaching $1 million before revocation.
Usage charged to someone else
Attackers look for exposed endpoints and valid keys, among other entry routes. They can then supply an intermediary that resells model usage. The million-dollar figure describes observed cases rather than a forecast for every small business. The question to examine is whether an outsider could use a consumption entitlement belonging to your company.
Resale rewards keeping access alive
BleepingComputer explains the resale intermediaries often called LLM mixers. Dark Reading adds analysis from Swimlane’s Nick Tausek: small validation requests can precede heavy consumption. Waiting solely for an abnormal bill can therefore miss an initial period of unauthorized use.
Identify every AI access owner
For a small team, begin with projects, service accounts and keys that authorize model calls. Identify each business owner and dependent application. A key shared across several demonstrations makes stopping suspicious usage harder without interrupting legitimate work. Include outside providers who configure these integrations in the review.
Connect permissions with consumption
Review access changes alongside billed usage. An unexpected key or permission deserves investigation even without a spending spike. For unauthorized access, follow the provider’s procedure to stop usage and invalidate credentials, then check legitimate integrations. Preserve evidence for support and investigation without copying secrets into incident notes.
How Soclyde relates
The LLMjacking investigation shows how an access key can carry rapid financial consequences. Soclyde organizes administrative credentials in an encrypted vault on devices and supports sharing with authorized colleagues. Credentials used automatically also need protection within their execution environment; revocation takes place with the issuing provider.
What to remember
Give every AI access credential an owner, a limited purpose and monitoring. Pair consumption alerts with identity review instead of waiting for a billing period to close. To structure your team’s professional access records, contact Soclyde.
