Malicious Run Key Persistence miasma-monitor from AsyncAPI npm Compromise

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 value named miasma-monitor, the Windows persistence installed by the AsyncAPI npm supply chain compromise import-time loader. The distinctive miasma named autostart relaunches the malicious payload at logon after a poisoned package is imported.

Related detections9 linkedT1547.001 — drag to rearrange
Suspicious File Written to Startup Folder by DllHost COM Surrogate
Suspicious Rundll32 Copied to Startup Folder via Blister Loader
Malicious Run Key Persistence NvmProtocal Launching NodePackages Payload
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
Malicious Run Key Persistence miasma-monitor from AsyncAPI npm Compromise
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.