Risk · R-074 · Adversarial ML & Model Integrity
Model weight theft
Proprietary weights or fine-tuned adapters are copied from storage, a pipeline or a supplier, taking the intellectual property and enabling attacks to be developed offline.
- Severity
- High
- Audience
- Heads-of · Practitioner
- Frameworks
- Principle 5 · Article 55 · AML.T0025
- Responsible AI domain
- Lifecycle stage
- Reviewed
- 2026-11-10
What it is
A model's weights are a file. Whoever has the file has the model: its capability, the investment behind it, and whatever it memorised. Theft by conventional means, such as compromised storage, an insider or a weak supplier, is quicker and more complete than extraction through the interface. Fine-tuned adapters are small, easily moved and often less well protected than the base model.
How it happens
- Weights are stored where many staff or systems can read them.
- A development or experiment-tracking system exposes artefact locations.
- A departing employee copies them.
- A hosting or fine-tuning supplier is compromised.
Why it matters
Beyond the commercial loss, the thief can study the model without limit: search for inputs that defeat it, recover training data, or remove its safeguards. Stolen weights cannot be recalled, and the organisation may not learn of the loss until a copy appears elsewhere. If the model was trained on personal data, the theft may also be a reportable breach.
Warning signs
- No inventory of where weights are stored.
- Access to artefact stores is broad, shared or unlogged.
- Large transfers from artefact storage.
- Supplier contracts are silent on custody of weights.
Who owns it
The model owner is accountable for the asset. Security owns the access standard and monitoring. Third-party risk covers suppliers who hold weights.
In practice
A fine-tuned underwriting model is kept in a storage bucket whose access list was widened during a migration and never narrowed. A contractor's compromised laptop is used to copy the bucket. The same pattern generalises to any model whose files are protected less carefully than the data used to train it.
Mitigating controls
Primary controls
- Model and data access control Preventive
- Restricts and logs access to weights wherever they are stored. Access to model weights, training data, pipelines and inference endpoints is granted by role, limited to need, logged and reviewed.
Supporting controls
- AI contract terms Directive
- Binds suppliers who hold the weights to equivalent protection. Contracts with AI suppliers cover data use, change notification, information and audit rights, sub-contracting, incident notification, liability and exit.
- AI incident classification and playbooks Corrective
- Defines the response when weights are found to have been taken. The kinds of AI failure are defined in the incident process with severity criteria, each has a playbook, and responders are trained and exercised in using them.
- Secure AI development pipeline Preventive
- Secures the systems the weights pass through. The pipelines and tooling that train, evaluate and deploy models are subject to the security controls of production software delivery, including review, scanning and segregation of environments.
Framework and clause references
| Framework | Clause | Title |
|---|---|---|
| Code of Practice for the Cyber Security of AI | Principle 5 | Identify, track and protect your assets Protection of model assets. |
| EU AI Act | Article 55 | Obligations of providers of general-purpose AI models with systemic risk Cybersecurity of the model for systemic-risk providers. |
| MITRE ATLAS | AML.T0025 | Exfiltration via Cyber Means Exfiltration by conventional cyber means. |
Sources
- EU AI Act: Regulation (EU) 2024/1689 European Union (EUR-Lex) · official text
- MITRE ATLAS MITRE · framework
Related terms
How to cite
Axiom Verity (2026). Model weight theft. Reference Library, R-074. https://axiom-verity.com/risks/model-weight-theft. Reviewed 2026-11-10.
Found an error or a better source? Report a correction.