Malicious Axios npm Compromise Run Key Persistence as MicrosoftUpdate (via registry_set)

PremiumReviewedSigma · High · v1
Product
windows
Category
registry_set
Author
HuntRule
Published
2026-11-05
Updated
2026-11-05

ATT&CK techniques

Initial Access → Priv Esc
  1. Recon

  2. Resource Dev

  3. Execution

  4. Defense Evasion

  5. Cred Access

  6. Discovery

  7. Lateral Movement

  8. Collection

  9. C2

  10. Exfiltration

  11. Impact

What it detects

This rule detects creation of a HKCU Run key value named MicrosoftUpdate which the trojanized axios npm versions 1.14.1 and 0.30.4 use to persist their second-stage Windows RAT. The masquerade as a Microsoft update in the per-user Run key combined with an untrusted payload path indicates supply-chain implant persistence.

Related detections9 linkedT1547.001 — drag to rearrange
Malicious Axios npm Compromise macOS Persistence com.apple.act.mond (via file_event)
Malicious Axios npm Compromise C2 Beacon to sfrclak and callnrwise (via dns_query)
Suspicious Run Key Persistence via Reg Add
Suspicious Run Key Persistence Pointing to ProgramData Executable
Possible WSHRAT Persistence via Run Key Silent Script Execution
Malicious Run Key Persistence via wininfo64 Path by Italian Infostealer (via registry_set)
Suspicious Startup Folder LNK Persistence Creation via File System (via file_event)
Suspicious XWorm Persistence Run Key Pointing to Batch Loader via ScreenConnect Lure (via registry_set)
Suspicious Run Key Persistence Named AppResolver (via registry_set)
Malicious Axios npm Compromise Run Key Persistence as MicrosoftUpdate (via registry_set)
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.