Suspicious Cmd Execution via WMI

edit

Suspicious Cmd Execution via WMI

edit

Identifies suspicious command execution (cmd) via Windows Management Instrumentation (WMI) on a remote host. This could be indicative of adversary lateral movement.

Rule type: eql

Rule indices:

logs-endpoint.events.*
winlogbeat-*
logs-windows.*

Severity: medium

Risk score: 47

Runs every: 5 minutes

Searches indices from: now-9m (Date Math format, see also Additional look-back time)

Maximum alerts per execution: 100

Tags:

Elastic
Host
Windows
Threat Detection
Execution

Version: 3 (version history)

Added (Elastic Stack release): 7.11.0

Last modified (Elastic Stack release): 7.12.0

Rule authors: Elastic

Rule license: Elastic License v2

Rule query

edit

process where event.type in ("start", "process_started") and
process.parent.name : "WmiPrvSE.exe" and process.name : "cmd.exe" and
process.args : "\\\\127.0.0.1\\*" and process.args : ("2>&1", "1>")

Threat mapping

edit

Framework: MITRE ATT&CK^TM

Tactic:
- Name: Execution
- ID: TA0002
- Reference URL: https://attack.mitre.org/tactics/TA0002/
Technique:
- Name: Windows Management Instrumentation
- ID: T1047
- Reference URL: https://attack.mitre.org/techniques/T1047/

Rule version history

edit

Version 3 (7.12.0 release)

Updated query, changed from:

process where event.type in ("start", "process_started") and
process.parent.name == "WmiPrvSE.exe" and process.name == "cmd.exe"
and wildcard(process.args, "\\\\127.0.0.1\\*") and process.args in
("2>&1", "1>")

Version 2 (7.11.2 release)

Formatting only

« Suspicious Child Process of Adobe Acrobat Reader Update Service Suspicious DLL Loaded for Persistence or Privilege Escalation »