huntrule

Windows Process Execution: Microsoft.NodejsTools.PressAnyKey.exe Child Spawns

Flags child processes started by Microsoft.NodejsTools.PressAnyKey.exe, which may be abused to run arbitrary binaries.

FreeReviewedSigma · Medium · v1
Product
windows
Category
process_creation
Author
Florian Roth (Nextron Systems), Nasreddine Bencherchali (Nextron Systems) (SigmaHQ), DRL 1.1
Published
2022-01-11
Updated
2026-07-30
AnalysisDetection

ATT&CK techniques

Defense Evasion

  1. Recon

  2. Resource Dev

  3. Initial Access

  4. Execution

  5. Persistence

  6. Priv Esc

  7. Defense Evasion

  8. Cred Access

  9. Discovery

  10. Lateral Movement

  11. Collection

  12. C2

  13. Exfiltration

  14. Impact

What it detects

This rule identifies Windows process creation events where a child process is spawned by Microsoft.NodejsTools.PressAnyKey.exe. Attackers can abuse this parent process to launch arbitrary binaries, helping them execute code under a trusted-looking process context. The detection relies on parent-child relationships in process creation telemetry, matching the parent image suffix.

Reporting behind it

Related detections9 linkedT1218 — drag to rearrange
Suspicious Cabinet Extraction of Masqueraded vstm Archive via extrac32
Malicious DLL Execution via Wuauclt Update Handler (via process_creation)
Malicious aspnet_compiler.exe Injection Host Spawned by PowerShell via process_creation
Malicious regsvcs LOLBin Loading Ransomware DLL from UNC Path
Suspicious RegAsm or RegSvcs Spawned by Script Host (via process_creation)
Suspicious Extexport DLL Side-Loading Execution
Malicious ClickFix Execution Chain Spawning MSHTA via Pcalua on EtherRAT Infection
Suspicious TALONITE Certutil LOLBIN Decode and Download Abuse (via process_creation)
Suspicious Renamed git Binary gcmd.exe Execution (via process_creation)
Windows Process Execution: Microsoft.NodejsTools.PressAnyKey.exe Child Spawns
Pivot detection · T1218 · 9 related

Detection content is published as a reviewed draft. Tune thresholds and exclusions against your own telemetry before enabling this rule for alerting.