Windows Management Instrumentation Event Subscription

Executive Summary

Windows Management Instrumentation Event Subscription (T1546.003) is a MITRE ATT&CK technique associated with Privilege Escalation, Persistence. Adversaries may establish persistence and elevate privileges by executing malicious content triggered by a Windows Management Instrumentation (WMI) event subscription.

Why Attackers Use It

Attackers use Windows Management Instrumentation Event Subscription because it provides a reliable way to advance their objective within the Privilege Escalation, Persistence tactic, often with a favorable balance of impact versus detectability on Windows environments. Defenders should assess this behavior in the context of the affected platform and adjacent activity rather than treating it as a standalone indicator.

MITRE Description

Adversaries may establish persistence and elevate privileges by executing malicious content triggered by a Windows Management Instrumentation (WMI) event subscription. WMI can be used to install event filters, providers, consumers, and bindings that execute code when a defined event occurs. Examples of events that may be subscribed to are the wall clock time, user login, or the computer's uptime.(Citation: Mandiant M-Trends 2015)

Adversaries may use the capabilities of WMI to subscribe to an event and execute arbitrary code when that event occurs, providing persistence on a system.(Citation: FireEye WMI SANS 2015)(Citation: FireEye WMI 2015) Adversaries may also compile WMI scripts – using mofcomp.exe –into Windows Management Object (MOF) files (.mof extension) that can be used to create a malicious subscription.(Citation: Dell WMI Persistence)(Citation: Microsoft MOF May 2018)

WMI subscription execution is proxied by the WMI Provider Host process (WmiPrvSe.exe) and thus may result in elevated SYSTEM privileges.

Attack Flow

1. Attacker gains the prerequisite access or context described below.
2. Attacker executes Windows Management Instrumentation Event Subscription to achieve its tactical objective (Privilege Escalation, Persistence).
3. Resulting access/data/effect is leveraged to advance the broader attack chain (see Related Techniques).

Prerequisites

• Platform(s): Windows
• ATT&CK does not define one universal permission requirement for this technique. Establish the required access from the observed implementation and affected platform.

Common Tools

• Tool attribution is implementation-specific. Use ATT&CK procedure examples and local telemetry to identify the binaries, services, scripts, accounts, or cloud resources involved.

Commands

No universal command represents Windows Management Instrumentation Event Subscription. Capture the exact command line, arguments, parent process, account, host, and execution time from the investigated environment; do not operationalize unverified examples.

Network Traffic

• Network observability is implementation-dependent. Review DNS, proxy, firewall, flow, authentication, and packet telemetry around the activity window, then correlate remote endpoints and protocol behavior with host evidence.

Windows Events

Sysmon Events

Detection Opportunities

No MITRE detection guidance published for this technique.

Relevant ATT&CK Data Sources: N/A

Sigma Rules

A universal Sigma rule would create unreliable results because this technique has no single guaranteed observable. Build detection logic from a documented behavior and supported data source, scope it to the affected platform, and validate it against benign administrative activity before deployment.

Splunk Queries

Start with the data sources named in the detection section. Scope searches by asset, identity, and time window; correlate the primary behavior with preceding access and subsequent actions. A portable query is intentionally not provided where the technique lacks a universal schema or observable.

Investigation Workflow

1. Confirm that the observed behavior is consistent with Windows Management Instrumentation Event Subscription and rule out expected administrative or application activity.
2. Establish the first-seen time, initiating identity, source system, target system, and affected resources.
3. Collect relevant host, identity, network, cloud, and application telemetry for the surrounding time window.
4. Correlate parent and child activity, remote connections, file or configuration changes, and related ATT&CK techniques.
5. Determine scope by searching for the same observable across peer assets and identities.
6. Preserve volatile evidence and record confidence, assumptions, and telemetry gaps before containment.

Containment

1. Isolate affected host(s)/account(s) identified during investigation.
2. Revoke or rotate any credentials/tokens potentially exposed.
3. Apply the mitigations listed below where not already enforced.
4. Validate no related techniques (see Related Techniques) were chained against the same asset.

Mitigation

• M1018 -- User Account Management: User Account Management involves implementing and enforcing policies for the lifecycle of user accounts, including creation, modification, and deactivation.
• M1026 -- Privileged Account Management: Privileged Account Management focuses on implementing policies, controls, and tools to securely manage privileged accounts (e.g., SYSTEM, root, or administrative accounts).
• M1040 -- Behavior Prevention on Endpoint: Behavior Prevention on Endpoint refers to the use of technologies and strategies to detect and block potentially malicious activities by analyzing the behavior of processes, files, API calls, and other endpoint events.

Related Techniques

• T1047
• T1053.005
• T1059.001
• T1059.003
• T1070.004
• T1071.001
• T1082
• T1105
• T1546