Implant Internal Image T1525
- Tactic
- Persistence
- Platforms
- IaaS, Containers
- Version
- 2.2
- Created
- 04 September 2019
- Last modified
- 24 October 2025
- Contributors
- Yossi Weizman, Azure Defender Research Team; Vishwas Manral, McAfee; Praetorian
Adversaries may implant cloud or container images with malicious code to establish persistence after gaining access to an environment. Amazon Web Services (AWS) Amazon Machine Images (AMIs), Google Cloud Platform (GCP) Images, and Azure Images as well as popular container runtimes such as Docker can be implanted or backdoored. Unlike Upload Malware, this technique focuses on adversaries implanting an image in a registry within a victim’s environment. Depending on how the infrastructure is provisioned, this could provide persistent access if the infrastructure provisioning tool is instructed to always use the latest image.[1]
Offense vs defense T1525
Is defensive coverage keeping up with adversary use? Eight counts, each ranked against all 697 ATT&CK techniques. Attack sits left, defense right, so a shape leaning left means adversaries are better documented here than defenders are equipped. Hover any spoke for its percentile and the share of techniques that have more. The timeline below shows when each side arrived.
How it got here
Adversary activity (campaign spans) over cumulative rule output. Each source is plotted independently from zero, so neither line includes the other. Campaign dates are year-granularity.
Implant Internal Image detection strategy DET0334
MITRE names one behaviour worth catching for this technique and breaks it into 2 analytics, one per platform. Each carries the log sources it needs and the fields you tune per environment.
Detection Strategy for T1525 – Implant Internal Image
AN0946 · Containers
Implantation of malicious code into container images followed by registry push and use in new deployments.
Log sources
The data this analytic draws on. You do not need every component — each one you already collect covers part of it. Each links to its ATT&CK record.
| Data component | Name | Channel |
|---|---|---|
| Image CreationDC0015 | docker:daemon | docker build or docker commit commands followed by docker push to internal registry |
| Image ModificationDC0036 | docker:registry | push event of new image version from unrecognized user or context |
Tunable fields
MITRE calls these the analytic’s mutable elements: the thresholds and filters you set for your own environment.
| Field | What you tune |
|---|---|
| TimeWindow | Time threshold between image creation and use in deployment – typically rapid in adversarial activity. |
| UserContext | The expected users or service accounts performing image pushes. |
| RegistryNameRegex | Expected naming patterns for trusted registries. |
AN0947 · IaaS
Creation or modification of cloud virtual machine images (AMIs, custom images) with persistence mechanisms, followed by infrastructure provisioning that uses these implanted images.
Log sources
The data this analytic draws on. You do not need every component — each one you already collect covers part of it. Each links to its ATT&CK record.
| Data component | Name | Channel |
|---|---|---|
| Image CreationDC0015 | AWS:CloudTrail | RegisterImage |
| Image ModificationDC0036 | AWS:CloudTrail | ModifyImageAttribute |
| Instance StartDC0080 | AWS:CloudTrail | RunInstances |
Tunable fields
MITRE calls these the analytic’s mutable elements: the thresholds and filters you set for your own environment.
| Field | What you tune |
|---|---|
| IAMRole | Roles that are allowed to register and modify images should be scoped narrowly. |
| ImageTagRegex | Expected tags or naming patterns for images (e.g., 'golden-image', 'base-image'). |
| LaunchWindow | Time interval between image creation and instance launch. |
Periodically check the integrity of images and containers used in cloud deployments to ensure they have not been modified to include malicious software.
Several cloud service providers support content trust models that require container images be signed by trusted sources.
Limit permissions associated with creating and modifying platform images or containers based on the principle of least privilege.