@years20/n8n-nodes-utils-helper-dnpm
@years20/n8n-nodes-utils-helper-d is a confirmed malicious npm package (MAL-2026-13912) that executes malicious code on install (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-d (npm)
What this malware does
The package runs a hostile payload both from its declared postinstall hook (node callback.js) and at library load via index.js, which is byte-identical to callback.js and set as main. The payload runs id, collects the machine hostname, detects WSL, and reads /etc/ssh/ssh_host_ed25519_key.pub, then base64-encodes the data and sends it over HTTPS GET to jasabersama.id/portfolio-data.php with TLS verification disabled (rejectUnauthorized: false). The exfil query wraps the encoded data in a shell command framed as portfolio-data.php. The same script decodes a base64-embedded OpenSSH ed25519 private key to /tmp/pk, chmods it to 600, and attempts SSH logins to 127.0.0.1:22495 and 127.0.0.1:22 as users devuser, ubuntu, runner, node, root, chris, and user, reporting successful authentications back to jasabersama.id. Because the payload is duplicated at module load, it also fires when n8n or any consumer performs require('@years20/n8n-nodes-utils-helper-d'), bypassing --ignore-scripts.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Malicious packageFind 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-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 @years20/n8n-nodes-utils-helper-d across your stack and pipelines.
If you installed it — respond
Remove @years20/n8n-nodes-utils-helper-d from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If @years20/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 @years20/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 @years20/n8n-nodes-utils-helper-d-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.