Windows winget Installs Applications Using Local Manifest File

Flags winget.exe install commands that specify a local manifest file via -m/--manifest.

FreeReviewedSigma · Medium · v1
Product
windows
Category
process_creation
Author
Sreeman, Florian Roth (Nextron Systems), frack113 (SigmaHQ), DRL 1.1
Published
2020-04-21
Updated
2026-07-30

ATT&CK techniques

Execution
  1. Recon

  2. Resource Dev

  3. Initial Access

  4. Persistence

  5. Priv Esc

  6. Defense Evasion

  7. Cred Access

  8. Discovery

  9. Lateral Movement

  10. Collection

  11. C2

  12. Exfiltration

  13. Impact

What it detects

This rule identifies Windows processes where winget.exe is used to install software with a local manifest, by matching install-related command-line arguments along with manifest flags (-m or --manifest). Attackers can leverage winget to fetch and install attacker-controlled packages, allowing remote payload delivery followed by execution. The detection relies on process creation telemetry capturing the Image/OriginalFileName for winget.exe and the full command line arguments.

Related detections9 linkedT1059 — drag to rearrange
AutoIt Script Execution via A3X Payload
Suspicious Python Execution via Renamed Synaptics Binary
MSBuild Executing Non-Project File or Remote Payload
Possible Ivanti Pulse Connect Secure Command Injection via License Keys-Status Endpoint (via webserver)
Possible Craft CMS RCE via Query-String CLI Option Injection
Possible Aspera Faspex Pre-Auth RCE via YAML Deserialization in package_relay (via webserver)
Possible Sitecore Pre-Auth RCE via Report.ashx Insecure Deserialization (via webserver)
Possible WatchGuard Pre-Auth RCE via agent login XML-RPC CVE-2022-26318
Possible Oracle Opera CGI Webshell Command Execution via operabin
Windows winget Installs Applications Using Local Manifest File
Pivot detection · T1059 · 9 related

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