MITRE ATLAS 2026.09 / technique reference
AML.T0011.001
Malicious Package
MITRE source definition
Adversaries may develop malicious software packages that when imported by a user have a deleterious effect. Malicious packages may behave as expected to the user. They may be introduced via [AI Supply Chain Compromise](/techniques/AML.T0010). They may not present as obviously malicious to the user and may appear to be useful for an AI-related task.
Source modified 2026-05-27. Reproduced from the pinned ATLAS release; inline technique links resolve to local reference pages.
Parent, sub-techniques and ATT&CK references
Source-backed defensive context
MITRE mitigations
- AML.M0011 Restrict Library Loading
- AML.M0013 Code Signing
- AML.M0016 Vulnerability Scanning
- AML.M0018 User Training
- AML.M0023 AI Bill of Materials
MITRE case studies
- AML.CS0022 ChatGPT Package Hallucination · Exercise
- AML.CS0047 Code to Deploy Destructive AI Agent Discovered in Amazon Q VS Code Extension · Incident
These are explicit source relationships, not independently reproduced incidents or validated detection coverage.
Simulation and telemetry boundary
This is a technique reference page, not a runnable simulation. No ATLAS-specific telemetry mapping, local attack execution or detector validation is asserted. MITRE maturity describes its source evidence, not a 1200km lab result.
For broader context—not technique-specific control mappings—see AI Security, AI Security Course, and detection-validation methodology.
Provenance and attribution
Immutable MITRE ATLAS source · Import provenance · Attribution and transformation notice · Apache License 2.0
Copyright 2021-2026 MITRE. Source text and explicit relationships are retained; navigation, formatting and local links are provided by 1200km.
No explicit relationship in this pinned source.