AML.T0008.005 · AI Service Proxies

Explore 4 source-supported AI security cases for AML.T0008.005 · AI Service Proxies in MITRE ATLAS, with evidence, scope, and defensive analysis.

Risk category

Adversaries may utilize commercial proxy services that resell access to AI services such as frontier model APIs. This infrastructure can be used to conduct large-scale campaigns to perform [Exfiltration via AI Inference API](/techniques/AML.T0024) via distillation. Adversaries may also use this infrastructure to [Generate Malicious Commands](/techniques/AML.T0102) for offensive cyber operations, or to generate content for [Spearphishing via Social Engineering LLM](/techniques/AML.T0052.000). Commercial AI service proxies distribute traffic from different accounts and various cloud platforms. The mix of traffic can make malicious activity difficult to detect and block[[anthropic]]. Malicious actors conduct [LLM Jacking](https://atlas.mitre.org/studies/AML.CS0030) attacks to gain access to victim accounts which they then resell access to in their proxy services[[sysdig]].

Official framework source ↗ · Open interactive explorer ↗

Incident ·

Industrial-Scale Distillation Across U.S. Frontier AI Services

NSA, CISA and FBI attributed coordinated distillation campaigns to six China-based AI companies. Their September 2026 advisory describes fraudulent accounts, bulk subscriptions, gray-market proxies, cross-provider routing, request-metadata removal and hidden-reasoning prompts, followed by response collection and quality checks. Distillation trains a model from another model’s outputs; the advisory’s attribution and capability-assessment claims are attributed to the agencies, not presented as independently reproduced measurements or model-weight theft.

ATLAS annotations follow the source SecureFlow steps; they are not a MITRE endorsement of cross-framework mappings.

SecureFlow · Read the full case ↗

Incident ·

Model Distillation Campaigns Target Google AI Services

Google reported campaigns that used compromised credentials, fraudulent accounts and proxies to collect model outputs for distillation: training another model from a provider’s responses. A February 2026 reasoning-focused campaign exceeded 100,000 prompts; later campaigns included some above 100 million. Those are campaign query volumes, not model weights stolen or a measured replication success rate. Google says it disrupted accounts and reduced the usefulness of collected outputs.

ATLAS annotations follow the source SecureFlow steps; they are not a MITRE endorsement of cross-framework mappings.

SecureFlow · Read the full case ↗

Incident ·

Model Distillation Campaigns Targeting Anthropic Claude

Anthropic attributed more than 16 million exchanges through roughly 24,000 fraudulent accounts to DeepSeek, Moonshot AI and MiniMax. The flow distinguishes proxy access, authenticated accounts, distributed routing, inference-response collection and downstream model training. Provider-side hunting and verified limits act before outputs leave; potential harms from models lacking safeguards remain Anthropic’s risk assessment, not observed downstream victim counts.

ATLAS annotations follow the source SecureFlow steps; they are not a MITRE endorsement of cross-framework mappings.

SecureFlow · Read the full case ↗

Incident ·

LLM Jacking

Sysdig observed stolen cloud credentials used to probe hosted LLM access and logging, then support reverse-proxy access that could be resold. The entry exploit, possession of credentials, tool preparation and provider-side use are distinct steps. The flow preserves parallel preparation before service use. Potential daily costs are estimates; provider-native IAM and complete invocation telemetry constrain direct calls that bypass an application proxy.

ATLAS annotations follow the source SecureFlow steps; they are not a MITRE endorsement of cross-framework mappings.

SecureFlow · Read the full case ↗