Windows: Suspicious msiexec.exe Command-Line Writes Install Logs with /Y

Alerts on suspicious msiexec.exe executions using the /Y argument that are not consistent with common installer locations.

FreeReviewedSigma · Medium · v1
Product
windows
Category
process_creation
Author
frack113 (SigmaHQ), DRL 1.1
Published
2022-01-16
Updated
2026-07-30

ATT&CK techniques

Defense Evasion
  1. Recon

  2. Resource Dev

  3. Initial Access

  4. Execution

  5. Persistence

  6. Priv Esc

  7. Defense Evasion

  8. Cred Access

  9. Discovery

  10. Lateral Movement

  11. Collection

  12. C2

  13. Exfiltration

  14. Impact

What it detects

This rule flags process creation where msiexec.exe is launched with a command line containing " /Y", which can be used to direct installer-related output to an attacker-controlled location. Such proxy execution behavior matters because it can help adversaries run or stage payloads through a trusted Windows utility. The detection relies on Windows process creation telemetry, matching the msiexec.exe image path suffix and the presence of the /Y argument while excluding common legitimate paths.

Related detections9 linkedT1218.007 — drag to rearrange
Suspicious Remote MSI Package Installation via msiexec (via process_creation)
Suspicious Remote MSI Installation over WebDAV (via process_creation)
Suspicious MSI Installation from Public Music Directory via Msiexec (via process_creation)
Suspicious Msiexec Installation of Remote MSI from WebDAV Share (via process_creation)
Suspicious msiexec Remote Passive Install Loader
Suspicious Silent MSI Installation of Non-Standard BIN Payload via Msiexec (via process_creation)
Suspicious Antivirus Uninstallation via msiexec (via process_creation)
Suspicious Screensaver File Executed as Installer via process_creation
Suspicious Remote MSI Installation from Amazon S3 via msiexec
Windows: Suspicious msiexec.exe Command-Line Writes Install Logs with /Y
Pivot detection · T1218.007 · 9 related

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