Malicious Registry Run Key Persistence via AHealthDB by Stately Taurus

PremiumReviewedSigma · High · v1
Category
registry_set
Author
HuntRule
Published
2026-10-21
Updated
2026-10-21

ATT&CK techniques

Persistence → Priv Esc
  1. Recon

  2. Resource Dev

  3. Initial Access

  4. Execution

  5. Defense Evasion

  6. Cred Access

  7. Discovery

  8. Lateral Movement

  9. Collection

  10. C2

  11. Exfiltration

  12. Impact

What it detects

This rule detects creation of a Run key value named AHealthDB that launches SmadavProtect32.exe, matching the persistence mechanism used by Stately Taurus in cyberespionage against the Philippines government reported by Unit 42. The actor masquerades a Run entry to auto-start a sideloading host at logon which maintains footholds for espionage.

Related detections9 linkedT1547.001 — drag to rearrange
Suspicious PikaBot Autorun Persistence Pointing to AppData Microsoft Dropzone via registry_set
Malicious Live Ledger Persistence via Realter HD Audio Run Key via registry_set
Malicious APT15 Persistence via Nwsapagent Service or Run Key Registry Value
Malicious Team9 Persistence via BackUp Mgr Run Key
Malicious NetHealth Run Key Persistence
Suspicious File Written to Startup Folder by DllHost COM Surrogate
Suspicious Rundll32 Copied to Startup Folder via Blister Loader
Malicious Run Key Persistence miasma-monitor from AsyncAPI npm Compromise
Malicious Run Key Persistence NvmProtocal Launching NodePackages Payload
Malicious Registry Run Key Persistence via AHealthDB by Stately Taurus
Pivot detection · T1547.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.