CyberKit

Event IDs

Sysmon event 21

WmiEvent (WmiEventConsumerToFilter activity detected)

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

What it records

Logs when a WMI consumer binds to a filter, recording the consumer name and filter path that completes the subscription.

Why it matters

This is the final link tying a trigger condition (Event 19) to an action (Event 20), seeing all three together confirms a complete, functioning WMI persistence/execution chain.

What triggers it

Rare outside legitimate systems-management automation; strongly associated with completing a WMI event-subscription persistence mechanism.

Fields that carry the answer

Key fields
FieldWhat it tells you
ConsumerThe consumer path being bound, which links this event to the specific action defined in Event 20.
FilterThe filter path being bound, which links this event to the trigger condition defined in Event 19.
OperationWhether the binding was created, modified, or deleted, which confirms whether a full persistence chain was actively assembled or torn down.

In practice

An Event 21 record shows Consumer CommandLineEventConsumer.Name="SCM Event Log Consumer" bound to Filter __EventFilter.Name="SCM Event Log Filter" with Operation=Created: correlating this binding with the matching Event 19 and Event 20 confirms all three pieces of a WMI persistence subscription were assembled together, rather than an orphaned filter or consumer that was never wired up.

Sample record

Wmi binding:
RuleName: -
EventType: WmiBindingEvent
UtcTime: 2024-02-11 09:42:04.389
Operation: Created
Consumer: CommandLineEventConsumer=BotConsumer23
Filter: EventFilter=BotFilter82

ATT&CK techniques

Sources

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