CyberKit

WMI Abuse

Also called Windows Management Instrumentation Abuse.

Using Windows management plumbing to run code and move quietly.

What it is

Abusing Windows Management Instrumentation, a built-in management framework, to execute commands, query systems, or persist via event subscriptions. It is trusted, scriptable, and can operate locally or against remote hosts.

Why it matters

Because WMI is a normal administrative interface, its abuse blends into legitimate activity and can drive execution, discovery, lateral movement, and stealthy persistence. WMI activity logging and the repository are important but often overlooked evidence sources.

In practice

A permanent WMI event subscription is discovered silently launching a payload whenever the system boots.

What to look for

  • WmiPrvSE.exe spawning command shells or PowerShell.
  • New permanent event subscriptions: filters, consumers and bindings.
  • Remote WMI process creation tied to a network logon from another host.

Common mistake

Missing persistence because nothing is on disk. WMI subscriptions live in the repository, so check it directly.

Practice it nearby

CyberKit has no tool for this term itself. These are the closest places to practice it.

In the field

Well-known tools where this shows up on the job. They are listed to show the landscape, not as a recommendation.

  • Atomic Red Team Open source

    Small, scripted tests mapped to ATT&CK techniques, used to check whether a detection fires.

  • ATT&CK Navigator Open source

    Lays techniques out on the ATT&CK matrix so teams can mark coverage, gaps and threat profiles.

  • Microsoft Defender for Endpoint Commercial

    Tags its alerts with the ATT&CK techniques it observed on the host.

  • Sysmon Free

    Supplies the host telemetry that most technique detections are written against. Our notes.

Read next

Sources