OpenParable
Skip to content
← Back to skills

T1204.003_malicious-image

DevOps & Security

Adversaries may rely on a user running a malicious image to facilitate execution.

View on GitHub ↗
QUICK START

How to use this skill

Bring this guide into your coding agent with a prompt tailored to the tool you use.

  1. Open your project in Codex.
  2. Copy and paste the prompt below.
  3. Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/CyberStrikeus/CyberStrike/blob/HEAD/.cyberstrike/skill/mitre_attack/TA0002_execution/T1204.003_malicious-image/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/t1204-003-malicious-image, but wait for my approval before writing files or running scripts.

Copying this prompt does not install or run the skill. Review third-party files before use.

T1204.003 Malicious Image

Sub-technique of: T1204

High-Level Description

Adversaries may rely on a user running a malicious image to facilitate execution. 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 backdoored. Backdoored images may be uploaded to a public repository via Upload Malware, and users may then download and deploy an instance or container from the image without realizing the image is malicious, thus bypassing techniques that specifically achieve Initial Access. This can lead to the execution of malicious code, such as code that executes cryptocurrency mining, in the instance or container.

Adversaries may also name images a certain way to increase the chance of users mistakenly deploying an instance or container from the image (ex: Match Legitimate Resource Name or Location).

Kill Chain Phase

  • Execution (TA0002)

Platforms: IaaS, Containers

What to Check

  • Identify if Malicious Image technique is applicable to target environment
  • Check IaaS systems for indicators of Malicious Image
  • Check Containers systems for indicators of Malicious Image
  • Verify mitigations are bypassed or absent (4 known mitigations)
  • Assess detection coverage (1 detection strategies)

How to Test

Manual Testing

  1. Identify Attack Surface: Determine if the target environment is susceptible to Malicious Image by examining the target platforms (IaaS, Containers).

  2. Assess Existing Defenses: Review whether mitigations for T1204.003 are in place. If defenses are absent or misconfigured, this technique may be exploitable.

  3. Execute Test: Use tools and methods described in the MITRE ATT&CK page and external references below.

Note: No Atomic Red Team tests available for this technique. See Atomic Red Team GitHub for updates.

Remediation Guide

M1045 Code Signing

Utilize a trust model such as Docker Content Trust with digital signatures to ensure runtime verification of the integrity and publisher of specific image tags.

M1031 Network Intrusion Prevention

Network prevention intrusion systems and systems designed to scan and remove malicious downloads can be used to block activity.

M1017 User Training

Train users to be aware of the existence of malicious images and how to avoid deploying instances and containers from them.

M1047 Audit

Audit images deployed within the environment to ensure they do not contain any malicious components.

Detection

User Execution – Malicious Image (containers & IaaS) – pull/run → start → anomalous behavior (T1204.003)

Risk Assessment

FindingSeverityImpact
Malicious Image technique applicableHighExecution

CWE Categories

CWE IDTitle
CWE-94Improper Control of Generation of Code

References