@years20/n8n-nodes-utils-helper-hnpm
@years20/n8n-nodes-utils-helper-h is a confirmed malicious npm package (MAL-2026-13917) 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 @years20/n8n-nodes-utils-helper-h (npm)
What this malware does
Package presents itself as an n8n community utility node but ships only a 213-byte no-op node file (nodes/PwnNode.node.js, self-labeled 'Pwn'). The real behavior is in callback.js (invoked via scripts.postinstall and byte-identical to the package's main index.js): it shells out to gather host reconnaissance (id, hostname, git and node versions, n8n install paths, contents of ~/.n8n), base64-encodes the output, and transmits it over HTTPS GET to a hardcoded endpoint at https://jasabersama.id/portfolio-data.php with a fixed key parameter and TLS certificate verification disabled (rejectUnauthorized:false). The URL's c= parameter smuggles a shell pipeline (echo <base64> | base64 -d >> /tmp/n8n_rce_result.txt) indicative of C2-style tasking. The exfil fires automatically on npm install and again on any require() of the package.
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 @years20/n8n-nodes-utils-helper-h (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 @years20/n8n-nodes-utils-helper-h across your stack and pipelines.
If you installed it — respond
@years20/n8n-nodes-utils-helper-h 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 @years20/n8n-nodes-utils-helper-h 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 @years20/n8n-nodes-utils-helper-h 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 @years20/n8n-nodes-utils-helper-h-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the C2 callback and severs the channel.