# Hunting For Lateral Movement Via Wmi

> Detects WMI-based lateral movement (e.g.

Detects WMI-based lateral movement (e.g. wmic process call create,

- Page: https://ss33.ai/skills/mukul975/hunting-for-lateral-movement-via-wmi-17602383564
- Publisher: mukul975
- Category: [Security](https://ss33.ai/skills/category/security-w9g95g) › [Threat intel & forensics](https://ss33.ai/skills/category/security-w9g95g/threat-intel-and-forensics-rt4m7u)
- License: Apache-2.0
- Source: https://github.com/mukul975/anthropic-cybersecurity-skills/blob/54a798831d2266a3ca61ce68a7acb80b81160d57/skills/hunting-for-lateral-movement-via-wmi/SKILL.md

## Skill

SKILL.md: https://ss33.ai/api/v1/ss33/download/mukul975/hunting-for-lateral-movement-via-wmi-17602383564

# Hunting for Lateral Movement via WMI

## Overview

Windows Management Instrumentation (WMI) is commonly abused for lateral movement via `wmic process call create` or Win32_Process.Create() to execute commands on remote hosts. Detection focuses on identifying WmiPrvSE.exe spawning child processes (cmd.exe, powershell.exe) in Windows Security Event ID 4688 and Sysmon Event ID 1 logs, along with WMI-Activity/Operational events (5857, 5860, 5861) for event subscription persistence.


## When to Use

- When investigating security incidents that require hunting for lateral movement via wmi
- When building detection rules or threat hunting queries for this domain
- When SOC analysts need structured procedures for this analysis type
- When validating security monitoring coverage for related attack techniques

## Prerequisites

- Windows Security Event Logs with Process Creation auditing enabled (Event 4688 with command line)
- Sysmon installed with Event ID 1 (Process Creation) configured
- Python 3.9+ with `python-evtx`, `lxml` libraries
- Understanding of WMI architecture and WmiPrvSE.exe behavior

## Steps

### Step 1: Parse Process Creation Events
Extract Event ID 4688 and Sysmon Event 1 entries from EVTX files.

### Step 2: Detect WmiPrvSE Child Processes
Flag processes where ParentImage/ParentProcessName is WmiPrvSE.exe, indicating remote WMI execution.

### Step 3: Analyze Command Line Patterns
Identify suspicious command lines matching WMI lateral movement patterns (cmd.exe /q /c, output redirection to admin$ share).

### Step 4: Check WMI Event Subscriptions
Parse WMI-Activity/Operational log for event consumer creation indicating persistence.

## Expected Output

JSON report with WMI-spawned processes, suspicious command lines, WMI event subscription alerts, and timeline of lateral movement activity.