User Execution (T1204) is a MITRE ATT&CK technique in the Execution tactic. SOC analysts detect it by monitoring for XDR, SIEM events, behavioral anomalies, and the specific indicators described in this detection guide. Practice detection in SOCSimulator Operations.
An adversary may rely upon specific actions by a user in order to gain execution. Users may be subjected to social engineering to get them to execute malicious code by, for example, opening a malicious document file or link. These user actions will typically be observed as follow-on behavior from forms of phishing. While User Execution frequently occurs shortly after initial access through phishing, it can also be triggered by drive-by compromise, malvertising, or watering hole attacks. Adversaries craft convincing lures such as fake invoices, shipping notifications, or security alerts that prompt users to enable macros, click links, or open attachments. The effectiveness of this technique relies heavily on the urgency or legitimacy of the social engineering pretext used to trick users into taking the desired action against their better judgment or security training.
“User Execution is documented as technique T1204 in the MITRE ATT&CK knowledge base under the Execution tactic. Detection requires visibility into XDR, SIEM telemetry.”
Detection Strategies
The following detection strategies help SOC analysts identify User Execution activity. These methods apply across XDR, SIEM environments and can be implemented as detection rules, correlation queries, or behavioral analytics in your security platform.
1
Monitor Office application processes for macro execution events, particularly when macros access the internet, spawn child processes, or write executable files to disk locations commonly used for malware staging.
2
Track file execution events for files downloaded from the internet or received via email, paying attention to the Zone.Identifier alternate data stream which indicates files sourced from external locations.
3
Correlate user-initiated file execution with subsequent network connections, registry modifications, or process creation to identify execution chains consistent with malware deployment following social engineering.
4
Alert on execution of files from temporary directories, user profile download folders, or uncommon paths such as AppData or Temp, which are frequently used as staging locations for malware delivered through user execution.
5
Monitor for the extraction and execution of files from password-protected archives, as attackers use password protection to bypass email gateway scanning and deliver malicious executables to end users.
Example Alerts
These realistic alert examples show what User Execution looks like in your security tools. Use them to tune detection rules and train analysts to recognize true positives versus false positives in live environments.
CriticalXDR
Malicious Office Macro Enabled by User
User enabled macros in a Word document received via email claiming to be an invoice from a vendor. Macro executed PowerShell to download and run a payload from hxxps://cdn-updates.net/update.exe. The executable was immediately flagged by behavioral analysis as exhibiting ransomware-like encryption behavior against user documents.
HighXDR
Executable File Run from Downloads Folder
User executed a file named AdobeFlashPlayer_Update.exe from the Downloads directory. The file has a Zone.Identifier mark indicating it was downloaded from the internet 8 minutes prior. Execution spawned cmd.exe and made DNS queries to three recently registered domains associated with the Agent Tesla keylogger family.
HighXDR
LNK File Execution Leading to Script Launch
Shortcut file execution triggered cmd.exe which invoked mshta.exe to retrieve and execute a remote HTA payload. The LNK file was delivered as an email attachment masquerading as a document preview. The HTA payload contains obfuscated VBScript that establishes persistence via a scheduled task and downloads additional tooling.
Practice Detecting User Execution
SOCSimulator provides hands-on training rooms where you investigate real-world attack scenarios including User Execution. Build detection skills with zero consequences — free forever.
SOC analysts detect User Execution (T1204) by monitoring XDR, SIEM telemetry for behavioral anomalies and specific indicators. Key detection methods include monitor office application processes for macro execution events, particularly when macros access the internet, spawn child processes, or write executa. SOCSimulator provides hands-on practice detecting this technique with realistic alerts.
What security tools are used to detect User Execution?
User Execution can be detected using XDR, SIEM platforms. XDR tools are particularly effective for this technique because they provide visibility into the execution phase of the attack chain. SOCSimulator simulates all three tool types for hands-on training.
How common is User Execution in real-world attacks?
User Execution is a well-documented MITRE ATT&CK technique in the Execution tactic. It appears in threat intelligence reports from multiple security vendors and has been observed in campaigns by various threat actor groups. SOCSimulator includes realistic User Execution scenarios based on documented attack patterns, helping analysts build detection intuition.
Can I practice detecting User Execution for free?
Yes. SOCSimulator offers free forever access to training scenarios, including Execution techniques like User Execution. You can investigate realistic alerts in guided Operations rooms, build detection skills with SIEM, XDR, and Firewall interfaces, and test yourself under pressure in Shift Mode. No credit card required.