Windows: File Creation of Get-Variable.exe in PowerShell WindowsApps Path

Alerts on creation of Get-Variable.exe in Local\Microsoft\WindowsApps, a potential cmdlet-path hijack.

FreeReviewedSigma · High · v2
Product
windows
Category
file_event
Author
frack113 (SigmaHQ), DRL 1.1
Published
2022-04-23
Updated
2026-07-31

ATT&CK techniques

Persistence → Defense Evasion
  1. Recon

  2. Resource Dev

  3. Initial Access

  4. Execution

  5. Cred Access

  6. Discovery

  7. Lateral Movement

  8. Collection

  9. C2

  10. Exfiltration

  11. Impact

What it detects

This rule flags creation of a file named Get-Variable.exe under the default WindowsApps directory path used during PowerShell execution. Attackers may abuse filename/path search behavior by introducing a malicious executable that could be invoked instead of the legitimate PowerShell cmdlet. The detection relies on Windows file creation telemetry that includes the target filename and supports suffix matching.

Related detections9 linkedT1027 — drag to rearrange
Malicious FIN7 Powertrash Loader Execution via Obfuscated PowerShell (via process_creation)
Suspicious XOR Obfuscated PowerShell from ClickFix Distribution
Suspicious PowerShell Executing Code from Environment Variable (via process_creation)
Suspicious Payload Staging in ProgramData IntelDriver Folder (via file_event)
Suspicious In-Memory Runspace Execution via PowerShell Script Block
Suspicious Python Inline Deobfuscation and Execution One-Liner
Suspicious PowerShell Reflective Assembly Load With Registry Property Read via Script Block (via ps_script)
Suspicious Archive Extraction From AppData Staging Folder via Process Creation
Suspicious Encoded PowerShell Using Base64 Stream Decompression Routines (via process_creation)
Windows: File Creation of Get-Variable.exe in PowerShell WindowsApps Path
Pivot detection · T1027 · 9 related

Changelog

v2
  1. v2
    Candidate ingested via manual entry.2026-07-31
  2. 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.