Suspicious Signed Script Proxy Execution via StartingScriptWrapper (via process_creation)

PremiumReviewedSigma · Medium · v1
Product
windows
Category
process_creation
Author
HuntRule
Published
2026-11-10
Updated
2026-11-10

ATT&CK techniques

Defense Evasion
  1. Recon

  2. Resource Dev

  3. Initial Access

  4. Execution

  5. Persistence

  6. Priv Esc

  7. Cred Access

  8. Discovery

  9. Lateral Movement

  10. Collection

  11. C2

  12. Exfiltration

  13. Impact

What it detects

This rule detects PowerShell invoking StartingScriptWrapper.ps1, the Advanced Installer PSFLauncher helper abused by the MSIX-packaged IDAT loader variant to proxy execution of its malicious update.ps1 through a signed script. Adversaries leverage the signed wrapper to launch attacker scripts under a trusted package while evading script-based controls, making detection useful for surfacing the loader stage before payload download.

Related detections9 linkedT1216 — drag to rearrange
Suspicious PowerShell Execution via SyncAppvPublishingServer LOLBIN
PowerShell Proxy Execution via SyncAppvPublishingServer (via process_creation)
Malicious Command Injection via SyncAppvPublishingServer VBS LOLBin (via process_creation)
Suspicious winrm.vbs LOLBAS Script Execution for Code Proxying
Windows: Code execution via Pester.bat invoked by PowerShell (Invoke-Pester/Get-Help)
Windows: Uncommon Child Processes Spawned by sigverif.exe
Windows: Suspicious CustomShellHost.exe execution spawned by non-Explorer parent
PowerShell: Signed UtilityFunctions.ps1 Loading Managed DLL via Proxy Execution
Windows PowerShell Script Proxy Execution via CL_mutexverifiers.ps1
Suspicious Signed Script Proxy Execution via StartingScriptWrapper (via process_creation)
Pivot detection · T1216 · 9 related

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