Malicious Winlogon Shell Hijack Loading MSBuild

PremiumReviewedSigma · High · v1
Product
windows
Category
registry_set
Author
HuntRule
Published
2026-09-27
Updated
2026-09-27

ATT&CK techniques

Execution → Defense Evasion
  1. Recon

  2. Resource Dev

  3. Initial Access

  4. Defense Evasion

  5. Cred Access

  6. Discovery

  7. Lateral Movement

  8. Collection

  9. C2

  10. Exfiltration

  11. Impact

What it detects

This rule detects the Winlogon Shell value being altered to reference MSBuild which the Dark Pink APT uses to persist and proxy execute code at logon through a trusted developer binary. The Shell key should only launch explorer.exe so any MSBuild reference signals abuse. It matters because it combines stealthy persistence with signed binary proxy execution.

Related detections9 linkedT1127.001 — drag to rearrange
Malicious Winlogon Shell Persistence Modification in KamiKakaBot Chain (via registry_set)
Suspicious Winlogon AutoAdminLogon Credential Persistence via registry_set (via registry_set)
PowerShell Launching MSBuild for Reflective Code Execution in KamiKakaBot Chain (via process_creation)
Suspicious Winlogon Shell Registry Persistence via CharmingCypress
Suspicious MSBuild Execution Spawned by Interactive Shell for Code Proxying (via process_creation)
Suspicious MSBuild Spawned by PowerShell (via process_creation)
Suspicious MSBuild Execution of Project File from ProgramData (via process_creation)
Malicious MSBuild Execution of Downloaded csproj Project File (via process_creation)
Suspicious MSBuild Inline Task Compilation of mini.xml
Malicious Winlogon Shell Hijack Loading MSBuild
Pivot detection · T1127.001 · 9 related

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