Operator On The Wire
Join
← Back to Knowledge Base
BLUE TEAM / THREAT HUNT / WINDOWS / EXECUTION

MSI Abuse

This note documents detection patterns related to MSI Abuse within Windows environments.


Direct Indicators

LogEvent IDMeaningForensic ValueNotes
Security4688Process creationCriticalDetects msiexec.exe execution and arguments.
Sysmon1Process creationCriticalBest source for parent lineage and command line.
Sysmon3Network connectionCriticalRemote MSI retrieval via HTTP/HTTPS/SMB.
Sysmon11File createHighMSI payload writes or extracted files.
Sysmon7Image loadedMediumDLL loads during MSI custom action abuse.
Application1033 / MsiInstallerHighMSI install records if logging enabled.

Indirect Indicators

IndicatorWhat To Look ForForensic ValueNotes
Remote MSI URLmsiexec /i http://...CriticalStrong malicious signal.
Silent install flags/qn, /quietHighCommon stealth flags.
MSI launches shellcmd / powershell childCriticalCustom action abuse.
User temp MSIPayload in temp/AppDataHighCommon staging path.
Unexpected parentOffice, browser, script hostCriticalStrong anomaly.
Short install then persistenceService/task followsCriticalStaged implant clue.

Common Tools

ToolUsage
msiexec.exeNative MSI execution
custom MSI packagesPayload delivery
PowerShellMSI wrapper execution
browserDownload + launch MSI

Relevant Artifacts

  • Security Event ID 4688
  • Sysmon Event IDs 1, 3, 7, 11
  • Application log:
    • MsiInstaller
  • Prefetch:
    • MSIEXEC.EXE
  • MSI files
  • Amcache / ShimCache
  • MFT / USN for MSI path
  • EDR process tree

MITRE ATT&CK References

  • T1218.007 Msiexec

Decision Tree

  1. Local or remote MSI?

    • Local file
    • URL
    • Share
  2. Silent flags present?

    • /qn
    • /quiet
  3. Child processes?

    • cmd
    • powershell
    • service install
  4. Parent suspicious?

    • Office
    • Browser
    • Script host
  5. Expand:

    • Extracted files
    • Persistence
    • Network
  6. Scope:

    • Single MSI
    • Campaign installer
    • Multi-host deployment

Example Detection Templates

KQL

SecurityEvent
| where EventID == 4688
| where NewProcessName endswith "msiexec.exe"
| project TimeGenerated, Computer, ParentProcessName, CommandLine
Sysmon
| where EventID == 3
| where Image endswith "\\msiexec.exe"
| project TimeGenerated, Computer, DestinationIp, DestinationPort

EQL

process where process.name == "msiexec.exe"
sequence by host.name with maxspan=5m
  [ process where process.name == "msiexec.exe" ]
  [ network where process.name == "msiexec.exe" ]

Sigma

title: MSI Abuse Detection
id: 9a2c7d31-msi-abuse
status: experimental
description: Detects suspicious msiexec usage
references:
  - https://attack.mitre.org/
author: Vergil
date: 2026-03-07
logsource:
  product: windows
  service: security
detection:
  selection:
    NewProcessName|endswith: '\msiexec.exe'
  condition: selection
fields:
  - ParentProcessName
  - CommandLine
falsepositives:
  - Legitimate software installs
level: medium
tags:
  - attack.execution
  - attack.t1218.007

Mitigation & Hardening

Control AreaMitigationEffectivenessNotes
MSI command monitoringAlert on remote installsCriticalStrong signal
Silent install detectionFlag /qn usageHighValuable anomaly
Parent-child monitoringWatch unusual launchersCriticalStrong context
Application controlRestrict unsigned MSIHighReduce abuse
Preserve installer logsValuable forensic sourceHighHelps reconstruction