Windows MSI Exec Creates elevation_service.exe Under Edge Path (CVE-2021-41379)

Flags msiexec creating elevation_service.exe within the Microsoft Edge application directory, indicating potential LPE exploitation.

FreeReviewedSigma · Critical · v5
Product
windows
Category
file_event
Author
Florian Roth (Nextron Systems) (SigmaHQ), DRL 1.1
Published
2021-11-22
Updated
2026-07-31

ATT&CK techniques

Priv Esc
  1. Recon

  2. Resource Dev

  3. Initial Access

  4. Execution

  5. Persistence

  6. Defense Evasion

  7. Cred Access

  8. Discovery

  9. Lateral Movement

  10. Collection

  11. C2

  12. Exfiltration

  13. Impact

What it detects

This rule flags file creation activity where an msiexec.exe process targets an Edge application directory and creates an elevation_service.exe file. Such behavior is consistent with exploiting the InstallerFileTakeOver LPE scenario tied to CVE-2021-41379, where elevated file placement enables privilege escalation. It relies on Windows file event telemetry that includes the creating process path (msiexec.exe) and the created file path (elevation_service.exe) under the specified Edge directory.

Related detections9 linkedT1068 — drag to rearrange
Suspicious Modification of Privileged Authentication Binaries via Kernel LPE
Malicious EDR Evasion Driver Load from AnyDesk Directory via k.sys (via image_load)
Malicious Zemana Vulnerable Driver Load for EDR Termination (via image_load)
Suspicious EDRKillShifter Vulnerable Driver Load from User Temp Directory (via image_load)
Suspicious Process Explorer Kernel Driver Dropped as PED.sys via File Creation (via file_event)
Malicious Payload Download From copy.fail Exploit Host on Linux (via process_creation)
Suspicious su Execution From Uncommon Parent Process on Linux (via process_creation)
Possible noPac sAMAccountName Spoofing via Machine Account Rename
Possible macOS TCC Bypass via mdimport Loading Custom Spotlight Importer
Windows MSI Exec Creates elevation_service.exe Under Edge Path (CVE-2021-41379)
Pivot detection · T1068 · 9 related

Changelog

v5
  1. v5
    Candidate ingested via manual entry.2026-07-31
  2. v4
    Candidate ingested via manual entry.2026-07-31
  3. v3
    Candidate ingested via manual entry.2026-07-31
  4. v2
    Candidate ingested via manual entry.2026-07-31
  5. v1
    No changelog recorded for this version.2026-07-30

Detection content is published as a reviewed draft. Tune thresholds and exclusions against your own telemetry before enabling this rule for alerting.