Malicious axios NPM Supply Chain Persistence via MicrosoftUpdate Run Key

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

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 Run key value named MicrosoftUpdate under the Windows CurrentVersion Run path, a persistence mechanism dropped by the trojanized axios npm packages through their postinstall setup.js script. The masquerading value name mimics a legitimate Microsoft update task while pointing to attacker second-stage code that beacons to sfrclak.com. Detecting this key is important because it establishes reboot-persistent execution of supply-chain malware on developer hosts.

Related detections9 linkedT1547.001 — drag to rearrange
Malicious Registry Run Key Persistence Masquerading as MicrosoftUpdate
Suspicious Run Key Persistence Named AppResolver (via registry_set)
Suspicious SystemBC Persistence via Run Key to ProgramData Script
Suspicious Interlock RAT Persistence via HKCU Run Key Registration to AppData Payload (via process_creation)
Suspicious SOCKS Proxy Persistence via SystemBC PowerShell Run Key
Suspicious Run Key Persistence Referencing PowerShell Script via registry_set
Malicious Startup Persistence via WindowsDefenderSync Shortcut (via file_event)
Malicious PXA Stealer Persistence via Windows Update Service Run Key (via registry_set)
Suspicious NetSupport client32 Persistence via Run Key from ProgramData
Malicious axios NPM Supply Chain Persistence via MicrosoftUpdate Run Key
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.