Malicious APT15 Persistence via Nwsapagent Service or Run Key Registry Value

PremiumReviewedSigma · High · v1
Product
windows
Category
registry_set
Author
HuntRule
Published
2026-10-17
Updated
2026-10-17

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 registry modifications that register APT15 persistence under the Nwsapagent name in either a service key or an autorun Run key. Observed in NCC Group research on APT15 RoyalCli and RoyalDNS which persist via a Nwsapagent service and Run key. Masquerading persistence under a plausible service name is a hallmark of this espionage group.

Related detections9 linkedT1547.001 — drag to rearrange
Suspicious K7Soft Autostart Persistence
Malicious Team9 Persistence via BackUp Mgr Run Key
Malicious NetHealth Run Key Persistence
Possible Driver Enumeration via Driverquery for Rootkit Discovery
Suspicious File Written to Startup Folder by DllHost COM Surrogate
Suspicious Rundll32 Copied to Startup Folder via Blister Loader
Malicious Kernel Driver Load from User AppData Directory
Malicious Run Key Persistence miasma-monitor from AsyncAPI npm Compromise
Malicious Run Key Persistence NvmProtocal Launching NodePackages Payload
Malicious APT15 Persistence via Nwsapagent Service or Run Key Registry Value
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.