Windows Setup16.EXE Execution Triggered by Custom .LST File

Flags Windows Setup16.EXE being invoked with ' -m ' from its system parent process, potentially tied to custom .lst-driven execution.

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

ATT&CK techniques

Execution → Defense Evasion

What it detects

This rule identifies execution of Setup16.EXE when it is launched with a command line containing the parameter pattern ' -m ', under the specific parent process path C:\Windows\SysWOW64\setup16.exe. It focuses on cases where Setup16 can be invoked with an external .lst file that may direct additional program execution, which can be abused for stealthy utility execution. The detection relies on process creation telemetry, including the parent image and parent command line. It also excludes executions originating from C:\~MSSETUP.T\ to reduce noise.

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