@years18/n8n-nodes-utils-helper-unpm
@years18/n8n-nodes-utils-helper-u is a confirmed malicious npm package (MAL-2026-13865) 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-u (npm)
What this malware does
The package's postinstall script (duplicated as the main module) runs unconditionally on npm install. It executes id and hostname, base64-encodes the output, and transmits it as a query-string parameter to a hardcoded HTTPS endpoint at jasabersama.id/portfolio-data.php with TLS certificate validation explicitly disabled (rejectUnauthorized: false). The same lifecycle hook installs the Python impacket package system-wide via pip --break-system-packages and invokes /tmp/mhddos/start.py, an MHDDoS attack launcher, weaponizing the installer host for outbound denial-of-service activity. The URL also carries a c= parameter conveying a shell command that decodes attacker-controlled bytes into /tmp/n8n_rce_result.txt, providing a command-staging channel back to the same remote endpoint.
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-u (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-u across your stack and pipelines.
If you installed it — respond
Remove @years18/n8n-nodes-utils-helper-u 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-u 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-u 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-u-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.