huntrule

Windows Registry: Appx DebugPath Key for Potential Persistence

Detects registry set activity involving AppX DebugPath entries that may indicate persistence via packaged app debug configuration.

FreeReviewedSigma · Medium · v1
Product
windows
Category
registry_set
Author
frack113 (SigmaHQ), DRL 1.1
Published
2022-07-27
Updated
2026-07-30
AnalysisDetection

ATT&CK techniques

Persistence → Priv Esc

  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 Windows registry modifications where a TargetObject containing Microsoft-related packaged app debug path entries ends with \DebugPath. It also matches entries under the PackagedAppXDebug Microsoft AppX debug key where the TargetObject ends with \(Default). Such registry persistence mechanisms can be used by attackers to influence how packaged apps are launched or debugged. Detection relies on registry set telemetry that includes TargetObject paths.

Reporting behind it

Related detections9 linkedT1546.015 — drag to rearrange
Suspicious COM Hijack of ClickOnce Deployment Service CLSID (via registry_set)
Suspicious COM Hijack Via InprocServer32 Modification
Malicious COM Hijacking via TinyTurla CLSID InprocServer32 (via registry_set)
Suspicious dllhost.exe Spawned with CLSID and Anomalous Parent (via process_creation)
Suspicious COM Handler Hijack of MsCtfMonitor CLSID via CharmingCypress
Malicious COM Hijack of PSFactoryBuffer InprocServer32
Malicious APT-C-60 COM Hijack via SpyGlace CLSID InProcServer32 (via registry_set)
Malicious COM Hijack via CLSID InProcServer32 Registry Modification (via registry_set)
Malicious COM Object Hijack Pointing to a User-Writable DLL (via registry_set)
Windows Registry: Appx DebugPath Key for Potential Persistence
Pivot detection · T1546.015 · 9 related

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