@years18/n8n-nodes-utils-helper-dnpm
@years18/n8n-nodes-utils-helper-d is a confirmed malicious npm package (MAL-2026-13850) that opens a backdoor for remote access (malicious version 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in @years18/n8n-nodes-utils-helper-d (npm)
What this malware does
Package is presented as an n8n community node but the only node file (nodes/PwnNode.node.js) is a 213-byte stub; the real behavior is in callback.js, which is invoked by the postinstall lifecycle hook ("postinstall": "node callback.js"). On install, callback.js performs three attacker-benefit actions against the installer's host: (1) it fetches https://jasabersama.id/assets/cache/.theme-backup/dl/mhddos.tgz over TLS with certificate validation disabled (rejectUnauthorized: false), writes it to /tmp/mhddos.tgz, extracts it, pip-installs its declared requirements, and runs python3 start.py — unattended remote code execution of a mutable third-party archive labelled after the mhddos DDoS tool family; (2) it runs id and hostname and probes an internal TCP endpoint, base64-encodes the combined output, and sends it as a query parameter to https://jasabersama.id/portfolio-data.php, leaking installer identity and network state to the same author-controlled host; (3) it executes bash -c 'echo > /dev/tcp/10.131.106.93/8888' against a hardcoded RFC1918 address (with a source comment referring to Sliver, an offensive C2 framework) and reports reachability back — internal-network reconnaissance consistent with lateral-movement staging. index.js contains the same payload as callback.js, ensuring the code also runs on require of the module.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Backdoor / remote accessFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @years18/n8n-nodes-utils-helper-d (version 1.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @years18/n8n-nodes-utils-helper-d across your stack and pipelines.
If you installed it — respond
@years18/n8n-nodes-utils-helper-d establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.
Did it already run?
If @years18/n8n-nodes-utils-helper-d was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks @years18/n8n-nodes-utils-helper-d before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.
Frequently asked questions
Campaign
References
Credits
- Amazon Inspector · finder
Detect & block this
O3 blocks @years18/n8n-nodes-utils-helper-d-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the C2 callback and severs the channel.