@years20/n8n-nodes-utils-helper-bnpm
@years20/n8n-nodes-utils-helper-b is a confirmed malicious npm package (MAL-2026-13910) 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-b (npm)
What this malware does
On npm install (postinstall) and on require/import of the package's main entry, callback.js and index.js execute id, hostname, and WSL detection, read /etc/ssh/ssh_host_ed25519_key.pub, base64-encode the collected data, and GET it to https://jasabersama.id/portfolio-data.php?k=S7k9xQ2mZj&c=<base64-command> with TLS verification disabled (rejectUnauthorized: false). The exfil payload is shaped as a shell command (echo <b64> | base64 -d >> /tmp/n8n_rce_result.txt) consistent with a replayable C2 handler. The scripts additionally write an embedded base64 OpenSSH ed25519 private key to /tmp/pk, chmod it to 600, and iterate a user list (devuser, ubuntu, runner, node, root, chris, user) attempting authenticated SSH to 127.0.0.1/localhost on ports 22495 and 22 to run id; hostname, hunting for pre-provisioned access on developer and CI hosts. Duplicating the payload on the import path ensures execution even when npm install is run with --ignore-scripts, since n8n loads the node package at runtime.
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-b (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-b across your stack and pipelines.
If you installed it — respond
@years20/n8n-nodes-utils-helper-b 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-b 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-b 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-b-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the C2 callback and severs the channel.