CyberKit

Event IDs

Sysmon event 20

WmiEvent (WmiEventConsumer activity detected)

Channel: Microsoft-Windows-Sysmon/Operational. Category: WMI.

What it records

Logs the registration of a WMI event consumer (the action that executes when the bound filter's condition fires) recording the consumer name, log, and destination.

Why it matters

The consumer is where the actual malicious payload or command line lives in a WMI persistence chain, making this event especially valuable for recovering what an attacker configured to run.

What triggers it

Rare in normal operation; overwhelmingly associated with WMI-based persistence or fileless execution set up by malware or offensive tooling.

Fields that carry the answer

Key fields
FieldWhat it tells you
NameThe name of the WMI consumer: the pivot value for correlating with the matching Event 21 binding.
TypeThe consumer type, e.g. CommandLineEventConsumer or ActiveScriptEventConsumer, which tells you what kind of action will execute when the subscription fires.
DestinationThe actual command line or script that will run when the subscription fires. This is where the real payload lives, making it the single most important field in the WMI persistence chain.
OperationWhether the consumer was created, modified, or deleted, which mirrors the same anti-forensic-cleanup signal as in Event 19.

In practice

An Event 20 record shows Name="SCM Event Log Consumer", Type=CommandLineEventConsumer, and Destination powershell.exe -nop -w hidden -enc <base64>. Destination is the actual payload that will run whenever the bound filter's condition fires, giving the analyst the full command line without needing to touch the WMI repository directly.

Sample record

Wmi consumer:
RuleName: -
EventType: WmiConsumerEvent
UtcTime: 2024-02-11 09:42:04.117
Operation: Created
User: CORP\jdoe
Name: BotConsumer23
Type: CommandLineEventConsumer
Destination: cmd.exe /c powershell.exe -NoProfile -WindowStyle Hidden -EncodedCommand <base64>

ATT&CK techniques

Sources

Paste a record into Event XML or open a log in EVTX Reader.