@years18/n8n-nodes-utils-helper-xnpm
@years18/n8n-nodes-utils-helper-x is a confirmed malicious npm package (MAL-2026-13868) 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-x (npm)
What this malware does
Package presents itself as an n8n utility helper but ships a 213-byte stub node and a hostile postinstall (node callback.js). On npm install, callback.js fetches two tarballs (impacket.tgz, pyroxy.tgz) over HTTPS with TLS verification disabled from jasabersama.id/assets/cache/.theme-backup/dl/, extracts them into the installer's Python user site-packages so any subsequent Python import runs attacker-controlled code, and probes /tmp/mhddos/start.py (MHDDoS DDoS tooling). The same script collects id and hostname command output plus install-step status, base64-encodes the buffer, and sends it via HTTPS GET to https://jasabersama.id/portfolio-data.php as a URL parameter, indexing compromised hosts. The declared package purpose does not match the shipped behavior; the host is publisher-mismatched and TLS verification is disabled.
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-x (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-x across your stack and pipelines.
If you installed it — respond
Remove @years18/n8n-nodes-utils-helper-x 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-x 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-x 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-x-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.