A LOLBIN was copied to a different location

Cortex XDR Analytics Alert Reference by Alert name

Product
Cortex XDR
Last date published
2024-06-04
Category
Analytics Alert Reference
Order
Alert name

Synopsis

Activation Period

14 Days

Training Period

30 Days

Test Period

N/A (single event)

Deduplication Period

6 Hours

Required Data

  • Requires:
    • XDR Agent

Detection Modules

ATT&CK Tactic

Defense Evasion (TA0005)

ATT&CK Technique

Masquerading: Rename System Utilities (T1036.003)

Severity

Informational

Description

To evade detection, attackers may copy a LOLBIN executable to a different location.

Attacker's Goals

Command execution via lolbins and detection avoidance via file rename.

Investigative actions

  • Check whether the executing process is benign, and if this was a desired behavior as part of its normal execution flow.
  • Check the destination path of the lolbin and try to see if it's benign.

Variations

A LOLBIN was copied to a different location using a rare command line

Synopsis

ATT&CK Tactic

Defense Evasion (TA0005)

ATT&CK Technique

Masquerading: Rename System Utilities (T1036.003)

Severity

High

Description

To evade detection, attackers may copy a LOLBIN executable to a different location.

Attacker's Goals

Command execution via lolbins and detection avoidance via file rename.

Investigative actions

  • Check whether the executing process is benign, and if this was a desired behavior as part of its normal execution flow.
  • Check the destination path of the lolbin and try to see if it's benign.


A LOLBIN was copied to a different location using a rare command line via a commonly used method

Synopsis

ATT&CK Tactic

Defense Evasion (TA0005)

ATT&CK Technique

Masquerading: Rename System Utilities (T1036.003)

Severity

Low

Description

To evade detection, attackers may copy a LOLBIN executable to a different location.

Attacker's Goals

Command execution via lolbins and detection avoidance via file rename.

Investigative actions

  • Check whether the executing process is benign, and if this was a desired behavior as part of its normal execution flow.
  • Check the destination path of the lolbin and try to see if it's benign.