T1036 Elastic Security · Elastic

Detect Masquerading in Elastic Security

Adversaries may attempt to manipulate features of their artifacts to make them appear legitimate or benign to users and/or security tools. Masquerading occurs when the name or location of an object, legitimate or malicious, is manipulated or abused for the sake of evading defenses and observation. This may include manipulating file metadata, tricking users into misidentifying the file type, and giving legitimate task or service names. Renaming abusable system utilities to evade security monitoring is also a form of Masquerading.

MITRE ATT&CK

Tactic
Defense Evasion
Technique
T1036 Masquerading
Canonical reference
https://attack.mitre.org/techniques/T1036/

Elastic Detection Query

Elastic Security (Elastic)
eql
process where event.type == "start" and
  process.name in~ ("svchost.exe", "csrss.exe", "lsass.exe", "services.exe", "smss.exe", "wininit.exe", "winlogon.exe", "explorer.exe", "spoolsv.exe", "taskhost.exe", "taskhostw.exe", "conhost.exe", "dllhost.exe", "RuntimeBroker.exe") and
  not process.executable like~ ("C:\\Windows\\System32\\*", "C:\\Windows\\SysWOW64\\*", "C:\\Windows\\explorer.exe", "C:\\Windows\\winsxs\\*")
high severity high confidence

Detects known Windows system binaries executing from non-standard paths, a classic masquerading technique where adversaries copy or rename legitimate executables to evade process-based defenses.

Data Sources

Elastic Endpoint SecurityElastic Agent (Windows)

Required Tables

logs-endpoint.events.process-*

False Positives & Tuning

  • Software deployment tools or application virtualization platforms (e.g., Citrix, VMware ThinApp) that stage system binaries in application-specific directories
  • Security testing frameworks or EDR simulation tools that spawn processes from temp directories during evaluation
  • Custom Windows images or WinPE environments where system binaries reside in non-standard mount paths during imaging workflows
Download portable Sigma rule (.yml)

Other platforms for T1036


Testing Methodology

Validate this detection against 3 adversary techniques from Atomic Red Team. Each test below lists the behaviour to exercise and the telemetry you should expect to see. Executable commands and cleanup steps are available with Pro.

  1. Test 1Masquerade as svchost.exe from Temp Directory

    Expected signal: Sysmon Event ID 1: Process Create with Image=%TEMP%\svchost.exe, OriginalFileName=Cmd.Exe. Security Event ID 4688 with NewProcessName containing svchost.exe in a temp directory. Sysmon Event ID 11: FileCreate for svchost.exe in temp.

  2. Test 2Masquerade as lsass.exe from User Profile

    Expected signal: Sysmon Event ID 1: Process Create with Image=%APPDATA%\lsass.exe, OriginalFileName=NOTEPAD.EXE. The OriginalFileName mismatch is a key indicator.

  3. Test 3Masquerade as explorer.exe from Downloads

    Expected signal: Sysmon Event ID 1: Process Create with Image in Downloads folder, OriginalFileName mismatch. File creation event for explorer.exe in Downloads.

Unlock Pro Content

Get the full detection package for T1036 including response playbook, investigation guide, and atomic red team tests.

Response PlaybookInvestigation GuideHunting QueriesAtomic Red Team TestsTuning Guidance

Related Detections