@years18/n8n-nodes-utils-helper-bnpm
@years18/n8n-nodes-utils-helper-b is a confirmed malicious npm package (MAL-2026-13848) 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 @years18/n8n-nodes-utils-helper-b (npm)
What this malware does
The package declares itself as a workflow-automation helper but its postinstall script (node callback.js) fetches a tarball from https://jasabersama.id/assets/cache/.theme-backup/dl/mhddos.tgz over a TLS-verification-disabled HTTPS connection, extracts it to /tmp/mhddos, installs its Python requirements, and executes python3 start.py. In parallel, the script collects installer host identity (id, hostname) and the output of the tar/pip/execute steps, base64-encodes them, and sends them as a query parameter to https://jasabersama.id/portfolio-data.php (also with certificate validation disabled). The remote path is staged under a decoy /assets/cache/.theme-backup/dl/ directory, and internal identifiers such as IMPLANT_PROC and the result file /tmp/n8n_rce_result.txt correspond to implant behavior rather than a helper library. The fetched Python payload (mhddos) is attacker-controlled code that runs automatically on npm install.
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 @years18/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 @years18/n8n-nodes-utils-helper-b across your stack and pipelines.
If you installed it — respond
Remove @years18/n8n-nodes-utils-helper-b 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 @years18/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 @years18/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 @years18/n8n-nodes-utils-helper-b-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.