@years19/n8n-nodes-utils-helper-knpm
@years19/n8n-nodes-utils-helper-k is a confirmed malicious npm package (MAL-2026-13894) that opens a backdoor for remote access (malicious version 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in @years19/n8n-nodes-utils-helper-k (npm)
What this malware does
The package's postinstall script callback.js — duplicated byte-for-byte as index.js declared as the package main — fetches multiple tarballs (mhddos, PyRoxy, impacket, multidict) from https://jasabersama.id/assets/cache/.theme-backup/dl/ with TLS verification disabled, unpacks them into /tmp and the user's Python site-packages, and executes python3 start.py to launch UDP/TCP/GET flood traffic against 103.118.252.21. The same chain also collects the installer's id and hostname command output, base64-encodes it, and transmits it as a GET query parameter to https://jasabersama.id/portfolio-data.php with TLS verification disabled. Both triggers fire without user interaction: the postinstall hook runs on npm install, and the identical main entry re-runs the chain on require/import (including when n8n loads this as a community node). The package presents as an n8n utility helper but ships no such functionality; its only behavior is dropping and executing attacker-hosted DDoS tooling while beaconing host identity to the attacker's C2.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Backdoor / remote accessFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @years19/n8n-nodes-utils-helper-k (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 @years19/n8n-nodes-utils-helper-k across your stack and pipelines.
If you installed it — respond
@years19/n8n-nodes-utils-helper-k establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.
Did it already run?
If @years19/n8n-nodes-utils-helper-k 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 @years19/n8n-nodes-utils-helper-k 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 @years19/n8n-nodes-utils-helper-k-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the C2 callback and severs the channel.