Malicious Run Key Persistence NvmProtocal Launching NodePackages Payload

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

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 an autorun Run key named NvmProtocal or one referencing the NodePackages protocal.cjs payload, the Windows persistence dropped by the Mastra npm supply chain compromise. The misspelled Node branding launches PowerShell or Node from ProgramData at logon to maintain access after the malicious package installs.

Related detections9 linkedT1547.001 — drag to rearrange
Malicious Run Key Persistence miasma-monitor from AsyncAPI npm Compromise
Suspicious Run Key Persistence Masquerading as Google Update
Suspicious Mint Sandstorm VBScript Persistence via Run Key (via registry_set)
Malicious Marbled Dust OMServerService VBScript Dropped to Startup Folder
Malicious STOCKSTAY Registry Run Key Persistence via MARKETMAKER Binaries (via registry_set)
Suspicious Registry Run Key Persistence Masquerading as Dropbox
Suspicious Registry Run Key Persistence Masquerading as CanonPrinter
Suspicious Rundll32 Persistence via Registry Run Key (via registry_set)
Malicious UNC1549 OneDrive-Masquerading Run Key Persistence (via registry_set)
Malicious Run Key Persistence NvmProtocal Launching NodePackages Payload
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.