T1546.003sub-technique of T1546 Event Triggered Execution

Windows Management Instrumentation Event Subscription

Windows5 pieces on this siteT1546.003 on attack.mitre.org

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.

MITRE ATT&CK 19.2, retrieved 2026-09-12

If this is happening now

1

Checklists and playbooks to open while the alert is still live.

Detect it

2

Hunts and rules you can run, each stating what it needs and what else it returns.

The evidence it leaves

1

Where the traces live, and what each source proves and does not.

Practise it

1

Labs, timelines, evidence packs and tabletop scenarios to work before you need to.

Guided labMembers

Guided lab: the persistence that leaves almost no log

WMI event subscriptions run code on a condition you choose, survive reboots, live nowhere in the filesystem, and log nothing by default. The last of the persistence series, and the one that changes how you think about the other three.

T1546.003

how MITRE says to see it

Detect WMI Event Subscription for Persistence via WmiPrvSE Process and MOF Compilation

  • Monitor for creation of WMI EventFilter, EventConsumer, and FilterToConsumerBinding objects through WMI or MOF file execution. Detect command-line execution of `mofcomp.exe`, usage of `Register-WmiEvent` via PowerShell, and anomalous child processes of `WmiPrvSE.exe` that indicate triggered execution.

what reduces it

  • M1040 Behavior Prevention on Endpoint. On Windows 10, enable Attack Surface Reduction (ASR) rules to prevent malware from abusing WMI to attain persistence.
  • M1018 User Account Management. By default, only administrators are allowed to connect remotely using WMI; restrict other users that are allowed to connect, or disallow all users from connecting remotely to WMI.
  • M1026 Privileged Account Management. Prevent credential overlap across systems of administrator and privileged accounts.

the rest of T1546

The description, detection analytics and mitigations are reproduced from MITRE ATT&CK, version 19.2, under its terms of use. The checklists, hunts, labs and everything else linked here are this site’s.