@years20/n8n-nodes-utils-helper-anpm
@years20/n8n-nodes-utils-helper-a is a confirmed malicious npm package (MAL-2026-13909) 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-a (npm)
What this malware does
The package's postinstall script (callback.js) and its main module (index.js, byte-identical to callback.js) execute on both npm install and require(). They shell out to collect id, hostname, WSL indicators, and the local SSH host-key fingerprint, base64-encode the recon output, and send it to a hardcoded endpoint at https://jasabersama.id/portfolio-data.php with rejectUnauthorized: false. The payload also decodes an embedded base64 OpenSSH ed25519 private key to /tmp/pk (chmod 600) and iterates common local account names (devuser, ubuntu, runner, node, root, chris, user) attempting SSH into 127.0.0.1:22495 and 127.0.0.1:22, reporting successful logins back to the same external host. The exfil query string carries a URL-encoded shell command that the receiving PHP handler is expected to execute, indicating a server-side command channel. The trigger fires automatically at install time via scripts.postinstall and again whenever a consumer (e.g. n8n loading this custom node) imports the module.
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-a (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-a across your stack and pipelines.
If you installed it — respond
Remove @years20/n8n-nodes-utils-helper-a 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-a 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-a 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-a-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.