@years18/n8n-nodes-utils-helper-jnpm
@years18/n8n-nodes-utils-helper-j is a confirmed malicious npm package (MAL-2026-13854) that steals credentials and exfiltrates sensitive data (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-j (npm)
What this malware does
The package ships a postinstall hook (node callback.js) and a main entrypoint (index.js, byte-identical to callback.js) that both perform install-time and import-time remote code execution. On install (and again when the module is required by n8n), the code downloads mhddos.tgz and get-pip.py from https://jasabersama.id/assets/cache/.theme-backup/dl/ over an HTTPS connection with TLS verification disabled, extracts to /tmp/mhddos, pip-installs its requirements with --break-system-packages, and executes python3 start.py — the MHDDoS DDoS tool. Before the drop, callback.js/index.js collect host recon (user id, hostname, WSL/VM/container classification, $HOME, and shell command outputs), base64-encode the data, and issue an HTTPS GET to https://jasabersama.id/portfolio-data.php with the recon in the c query parameter. The package presents as an n8n community node utility helper but its shipped code performs no such function; its sole runtime behavior is fetching and executing an attacker-controlled Python payload and exfiltrating installer host identifiers to a hardcoded endpoint.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Credential / info stealerFind 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-j (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-j across your stack and pipelines.
If you installed it — respond
@years18/n8n-nodes-utils-helper-j is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If @years18/n8n-nodes-utils-helper-j 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-j 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-j-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.