T1610: Deploy Container
Tactics: Execution. Platforms: Containers.
Adversaries may deploy a container into an environment to facilitate execution or evade defenses.
MITRE's description
Adversaries may deploy a container into an environment to facilitate execution or evade defenses. In some cases, adversaries may deploy a new container to execute processes associated with a particular image or deployment, such as processes that execute or download malware. In others, an adversary may deploy a new container configured without network rules, user limitations, etc. to bypass existing defenses within the environment.
Telemetry that detects it
- Application Log Content
- Container Start
- Network Traffic Content
- Process Creation
Mitigations
- User Account Management
- Enforce the principle of least privilege by limiting container dashboard access to only the necessary users.
- Audit
- Scan images before deployment, and block those that are not in compliance with security policies.
- Network Segmentation
- Deny direct remote access to internal systems through the use of network proxies, gateways, and firewalls.
- Limit Access to Resource Over Network
- Limit communications with the container service to managed and secured channels, such as local Unix sockets or remote access via SSH.
Procedure examples
- Doki was run through a deployed container.
- Kinsing was run through a deployed Ubuntu container.
- Peirates can deploy a pod that mounts its node’s root file system, then execute a command to create a reverse shell on the node.
- TeamTNT has deployed different types of containers into victim environments to facilitate execution. TeamTNT has also transferred cryptocurrency mining software to Kubernetes clusters discovered within local IP address ranges.
MITRE ATT&CK Enterprise 19.2. © 2026 The MITRE Corporation. This work is reproduced and distributed with the permission of The MITRE Corporation.