UTD · Unauthorized Training Data

Explore 3 source-supported AI security cases for UTD · Unauthorized Training Data in Google SAIF 2.0, with evidence, scope, and defensive analysis.

Risk category

A model is trained or fine-tuned on data that is not authorized for that use. This includes data used without the required user consent, unlicensed copyrighted material, and data restricted by policy, contract, or law. The issue is whether the organization has permission to use the data for this model, even if the data is accurate and has not been maliciously modified.

Official framework source ↗ · Open interactive explorer ↗

Incident · · Practical overlap

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.

Why it relates: The primary account describes unauthorized use of the provider’s responses as training data. This is the reported authorization/contract boundary, not an independent court finding about copyright or every distillation use.

the campaigns attributed by NSA, CISA and FBI; capability distillation is distinguished from stealing original weights. Attribution and capability outcomes remain agency assessments. Hidden-reasoning prompts are attempts, not proof that the returned text was an internal trace. No autonomous agent deployment is inferred.

SecureFlow · Read the full case ↗

Incident · · Practical overlap

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.

Why it relates: The primary account describes unauthorized use of the provider’s responses as training data. This is the reported authorization/contract boundary, not an independent court finding about copyright or every distillation use.

Google’s compromised-account and fraudulent-account campaigns; capability distillation is distinguished from stealing original weights. The prompt totals are collection volumes, not measured replication success or model weights. No autonomous agent deployment or protected-reasoning recovery is established.

SecureFlow · Read the full case ↗

Incident · · Practical overlap

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.

Why it relates: The primary account describes unauthorized use of the provider’s responses as training data. This is the reported authorization/contract boundary, not an independent court finding about copyright or every distillation use.

Anthropic’s DeepSeek, Moonshot AI and MiniMax campaigns; capability distillation is distinguished from stealing original weights. The 24,000-account and 16-million-exchange figures do not quantify recovered weights or observed downstream harms. Potential harms remain Anthropic’s assessment; an agent deployment is not established.

SecureFlow · Read the full case ↗