Back to results

Windows Renamed Command Interpreter was Executed

The following analytic identifies a Windows command interpreter process being executed where it's process name does not match it's original file name attribute. Processes that have been renamed and executed may be an…

Description

The following analytic identifies a Windows command interpreter process being executed where it's process name does not match it's original file name attribute. Processes that have been renamed and executed may be an indicator that an adversary is attempting to evade defenses or execute malicious code.

Detection logic

Detection requirements

Platform
ContainersESXiIaaSIdentity ProviderLinuxmacOSNetwork DevicesOffice SuiteSaaSWindows

The rule states no platform. This is derived from the 2 ATT&CK techniques it maps to.

Known benign triggers

  • 3rd party software binaries sharing the same name as Windows command interpreter binaries may trigger false positives.

Detections can measure how the public catalogue is used — which detections people look for, and which pages bring them here. It sets a cookie that recognises this browser for 180 days. It is never linked to an account and never follows you to other sites. Privacy notice