Template -- Masquerading Match Legitimate Name (anomalous path)

SIGMA detection rule by WinstonRedGuard -- sigma plugin canonical templates · MIT

Canonical sigma detection template for MITRE ATT&CK T1036.005 (Masquerading Match Legitimate Name (anomalous path)). Synthetic exemplar from the WinstonRedGuard threat-intel corpus -- no actor binding; review and bind to your environment before deployment.

title: Template -- Masquerading Match Legitimate Name (anomalous path)
id: 7f460b66-5960-575e-8c4d-8be90a222317
status: experimental
description: Canonical sigma detection template for MITRE ATT&CK T1036.005 (Masquerading Match Legitimate Name (anomalous
  path)). Synthetic exemplar from the WinstonRedGuard threat-intel corpus -- no actor binding; review and bind to your environment
  before deployment.
references:
- https://attack.mitre.org/techniques/T1036/005/
author: WinstonRedGuard -- sigma plugin canonical templates
date: '2026-05-21'
logsource:
  category: process_creation
  product: windows
detection:
  selection_legit_name_anomalous_path:
    OriginalFileName:
    - svchost.exe
    - lsass.exe
    - explorer.exe
    - csrss.exe
    - winlogon.exe
    - services.exe
    - spoolsv.exe
  filter_canonical_path:
    Image|startswith:
    - C:\Windows\System32\
    - C:\Windows\SysWOW64\
  condition: selection_legit_name_anomalous_path and not filter_canonical_path
falsepositives:
- Portable applications run from a user profile or removable media by design
- Developer build output producing binaries with common system names in a project directory
- Vendor software that legitimately self-installs per-user (some chat and conferencing clients)
level: medium
tags:
- attack.t1036.005
- wrg.template
- wrg.tactic.stealth

[[ currentRule.title && currentRule.title.length > 60 ? currentRule.title.slice(0, 60) + '…' : currentRule.title ]]

b6d7f98f-e550-4139-b394-7f118d672795

Propose edits, view related rules, and engage with the community through comments.

Executable code, not a declarative rule

This submission is arbitrary [[ currentRule.format ? currentRule.format.toUpperCase() : '' ]] code, not a declarative detection rule — review it as you would any script before running it, and note that it cannot be safely aggregated or auto-executed alongside YARA/Sigma/Suricata/CRS rules.

Rejected pattern present

[[ reason ]]

What does this mean?

Format & documentation suggestions

Not a security issue — this rule is valid and was accepted as-is. These are optional fields/conventions its own format recommends, mainly affecting its quality score and how well it documents itself for other reviewers.

[[ reason ]]

What do these messages mean?

[[ currentRule.title && currentRule.title.length > 60 ? currentRule.title.slice(0, 60) + '…' : currentRule.title ]]

[[ currentRule.title ]]

Community Discussion