Curl or Wget Spawned via Node.js
This rule detects when Node.js, directly or via a shell, spawns the curl or wget command. This may indicate command and control behavior. Adversaries may use Node.js to download additional tools or payloads onto the…
Description
This rule detects when Node.js, directly or via a shell, spawns the curl or wget command. This may indicate command and control behavior. Adversaries may use Node.js to download additional tools or payloads onto the system.
Detection logic
Its licence does not clear it for publishing here
Sunturai publishes a detection's own text where the licence it arrived under has been reviewed and permits it, and Elastic License 2.0 has not. The query as its source wrote it, its canonical form and the hash that pins this revision are in the workspace record.
Detection requirements
- Platform
- ESXiLinuxmacOSNetwork DevicesWindows
The rule states no platform. This is derived from the 2 ATT&CK techniques it maps to.
- Log source category
- event_index
MITRE ATT&CK mappings
0 exclusive techniques.This is coverage no other published rule has; it is not this rule's total technique count.
No references are available for this detection.
From the source
- At source
- Open at source
- Upstream identifier
- d9af2479-ad13-4471-a312-f586517f1243
- Tagged by the source as
- Data Source: Auditd ManagerData Source: CrowdstrikeData Source: Elastic DefendData Source: Elastic EndgameData Source: SentinelOneData Source: SysmonData Source: Windows Security Event LogsDomain: EndpointNoise: MediumOS: LinuxOS: macOSOS: WindowsPerformance: NormalPlatform: LinuxPlatform: macOSPlatform: WindowsProfile: RecommendedResources: Investigation GuideRule Type: Event Correlation (EQL)Tactic: Command and ControlThreat: Download Tool AbuseThreat: Supply ChainUse Case: Threat Detection
Licence
- Published under
- Elastic License 2.0Read the licence
- Attribution
- Required
Authorship
- Written by
- Published
- Sep 20, 2026
- Version
- 3