ATT&CK Reference
Portfolio

TA0002 · EXECUTION

User Execution

T1204Linux · Windows · macOS · IaaS · Containersattack.mitre.org

The user opens the attachment, mounts the ISO, runs the installer, or pastes the ClickFix command.

Detect it with

Process trees rooted in a mail client or browser download directory; execution from temp, Downloads, or a mounted image.

Why it matters on shift

User Execution is one of the concrete ways adversaries achieve execution. Recognising it in telemetry lets you name the technique in your ticket and pivot to what came before and after.

What to look for next

After execution, the next tactic is usually Persistence. Search your telemetry for the transition before closing the ticket.

4 sub-techniques

How it shows up in practice

  1. T1204.001

    Malicious Link

    An adversary may rely upon a user clicking a malicious link in order to gain execution. Users may be subjected to social engineering to get them to click on a link that will lead to code execution.

  2. T1204.002

    Malicious File

    An adversary may rely upon a user opening a malicious file in order to gain execution. Users may be subjected to social engineering to get them to open a file that will lead to code execution.

  3. T1204.003

    Malicious Image

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

  4. T1204.004

    Malicious Copy and Paste

    An adversary may rely upon a user copying and pasting code in order to gain execution. Users may be subjected to social engineering to get them to copy and paste code directly into a Command and Scripting Interpreter.

Kill-chain context

← beforeInitial AccessExecutionafter →Persistence