Windows command prompt started by an abnormal process

Description

Windows command prompt started by an abnormal process

Query · wazuh

field win.eventdata.originalFileName="(?i)cmd\.EXE" AND field win.eventdata.parentImage="(?i)(explorer|cmd)\.EXE"

Fires when

Wazuh evaluates a chain top-down. Every rule above this one must match on the same event before this rule is tested at all.

  1. 92052 Windows command prompt started by an abnormal process anchor level 4 this rule
    field win.eventdata.originalFileName="(?i)cmd\.EXE" AND field win.eventdata.parentImage="(?i)(explorer|cmd)\.EXE"

Refined by

3 rules chain off this one, narrowing it further.

Rule dependencies

Depends on

  • composes · Wazuh if_group sysmon_event1
    856 rules in this analytic story
Raw source Windows command prompt started by an abnormal process · Wazuh XML
Esc
Published by Wazuh Core Ruleset ↗, licensed under GPLv2 ↗. Reproduced here unmodified. 
<rule id="92052" level="4">
    <if_group>sysmon_event1</if_group>
    <field name="win.eventdata.originalFileName" type="pcre2">(?i)cmd\.EXE</field>
    <field name="win.eventdata.parentImage" type="pcre2" negate="yes">(?i)(explorer|cmd)\.EXE</field>
    <options>no_full_log</options>
    <description>Windows command prompt started by an abnormal process</description>
    <mitre>
      <id>T1059.003</id>
    </mitre>
  </rule>

Detection rules belong to the projects that publish them and remain under their own licenses. This site indexes and links to them; it claims no rights in them.