Sigma · CVE exploitation
Node.js stack: Node.js server spawned a shell or download tool
- severity
- medium
- confidence
- 55/100
- generated
- 14 Nov 2026
- Linked CVE
- CVE-2023-22621 · CVE-2026-111497 · CVE-2026-126187 · CVE-2026-44267 · CVE-2026-92934
A node process started a shell or a download tool. In production that is rare; after RCE in a Node web framework it is the first thing an attacker does (crypto-miner and botnet droppers were seen this way after React2Shell). Not specific to one bug: it fires on code execution through the Node.js stack by any route. Attached to the 5 CVEs in this stack that skopnix reported in the last 30 days, newest CVE-2026-126187, CVE-2026-111497, CVE-2026-92934.
False-positive notes
Needs node as the PARENT and a shell / downloader as the child. Children whose command line names npm, npx, yarn, pnpm, git or node-gyp are excluded. Meant for servers: on developer machines it is noise even with the exclusions.
References
title: 'Skopnix - Node.js stack: Node.js server spawned a shell or download tool'id: 84f3c4c9-359e-592d-8cbb-a95271e88a34status: experimentaldescription: 'A node process started a shell or a download tool. In production that is rare; after RCE in a Node web framework it is the first thing an attacker does (crypto-miner and botnet droppers were seen this way after React2Shell). Not specific to one bug: it fires on code execution through the Node.js stack by any route. Attached to the 5 CVEs in this stack that skopnix reported in the last 30 days, newest CVE-2026-126187, CVE-2026-111497, CVE-2026-92934.'references: - https://skopnix.com/cve/CVE-2026-126187 - https://skopnix.com/cve/CVE-2026-111497 - https://skopnix.com/cve/CVE-2026-92934 - https://skopnix.com/cve/CVE-2026-44267 - https://skopnix.com/cve/CVE-2023-22621author: skopnixdate: '2026-11-14'tags: - attack.execution - attack.t1190 - attack.t1059.004 - attack.t1059.003 - cve.2026-126187 - cve.2026-111497 - cve.2026-92934 - cve.2026-44267 - cve.2023-22621logsource: category: process_creationdetection: selection_parent: ParentImage|re|i: '[/\\]node(\.exe)?$' selection_child: Image|re|i: '[/\\](sh|bash|dash|zsh|busybox|curl|wget|nc|ncat|socat|cmd\.exe|powershell\.exe|pwsh\.exe|certutil\.exe|bitsadmin\.exe|mshta\.exe)$' filter_dev: CommandLine|contains: - npm - npx - yarn - pnpm - 'git ' - node-gyp condition: selection_parent and selection_child and not filter_devfalsepositives: - Developer workstations and build hosts (npm / yarn / pnpm scripts, git, next build) start shells all day; they are excluded by command line - Apps that shell out by design (image tools, PDF renderers via child_process); baseline by hostlevel: mediumskopnix-sigma-cve-stack-nodejs-node-shell-60d02ad8.yml
How to deploy on Sigma
- Step 1
- Convert for your SIEM with sigma-cli / pySigma, e.g. sigma convert -t splunk -p sysmon rule.yml.
- Step 2
- Run it as a hunt first: every rule ships as status experimental.
- Step 3
- Promote to an alert once a week of results is clean on your data.
- Check
- The processing pipeline must map the logsource (firewall, dns, proxy, webserver, process_creation) to your field names.