Malicious PowerShell Masquerading as wt.exe in ProgramData via Axios npm Compromise (via process_creation)

PremiumReviewedSigma · High · v1
Product
windows
Category
process_creation
Author
HuntRule
Published
2026-07-09
Updated
2026-08-28

ATT&CK techniques

Execution → Defense Evasion
  1. Recon

  2. Resource Dev

  3. Initial Access

  4. Persistence

  5. Priv Esc

  6. Cred Access

  7. Discovery

  8. Lateral Movement

  9. Collection

  10. C2

  11. Exfiltration

  12. Impact

What it detects

This rule detects a PowerShell binary renamed to wt.exe and executed from ProgramData, a masquerading technique used by the malicious postinstall payload delivered through the compromised Axios npm package. Adversaries rename PowerShell to evade name-based detection while running follow-on scripts, so a PowerShell OriginalFileName under a wt.exe in ProgramData is a strong indicator of the supply chain implant.

Related detections9 linkedT1059.001 — drag to rearrange
Malicious Axios NPM RAT Renamed PowerShell Execution via wt.exe
Windows: Process executions matching Greenbug espionage tool indicators
Suspicious Scheduled Task Running PowerShell Every Minute (via process_creation)
Malicious Script Host Spawning PowerShell With Invoke-Expression (via process_creation)
Hidden PowerShell Archive Extraction via ExtractToDirectory
CastleLoader ClickFix PowerShell Hex Decode and Re-Execution
Malicious Fake Fortinet Patch Infostealer Execution (via process_creation)
Malicious Non-Interactive Encoded PowerShell Stager (via process_creation)
Malicious ActiveMQ Exploitation Java Spawning PowerShell Downloader (via process_creation)
Malicious PowerShell Masquerading as wt.exe in ProgramData via Axios npm Compromise (via process_creation)
Pivot detection · T1059.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.