@years18/n8n-nodes-utils-helper-qnpm
@years18/n8n-nodes-utils-helper-q is a confirmed malicious npm package (MAL-2026-13861) 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-q (npm)
What this malware does
@years18/n8n-nodes-utils-helper-q ships as a stub n8n community node (nodes/PwnNode.node.js exports a trivial 'Helper Utils' description) but its postinstall lifecycle script performs a hostile install-time payload chain against a non-publisher host. On npm install, the script fetches https://jasabersama.id/assets/cache/.theme-backup/dl/mhddos.tgz and pyroxy.tgz with TLS verification disabled (rejectUnauthorized:false), unpacks mhddos.tgz to /tmp/mhddos and pyroxy.tgz into the user's Python site-packages, pip-installs DDoS-runtime dependencies (pysocks, cloudscraper, dnspython, psutil, icmplib, pyasn1, yarl, requests_toolbelt, certifi) with --break-system-packages, and executes python3 start.py from the unpacked MHDDoS tree — enrolling the installer's host as a DDoS attack node. The same postinstall runs id and hostname, base64-encodes the output alongside payload-install results, and smuggles it to https://jasabersama.id/portfolio-data.php?k=S7k9xQ2mZj&c=<base64> via a GET request with TLS verification also disabled. The staging path (/assets/cache/.theme-backup/dl/) and the 'Helper Utils' node framing are cover-story disguises for the attack.
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-q (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-q across your stack and pipelines.
If you installed it — respond
Remove @years18/n8n-nodes-utils-helper-q 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-q 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-q 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-q-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.