Malicious code in @years18/n8n-nodes-utils-helper-q (npm)
--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (ab6ad174527240f5b3cf6eac2f078ff9a95cc3599926aca824d541c650f18a66) @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 code in @years18/n8n-nodes-utils-helper-q (npm)
Description
--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (ab6ad174527240f5b3cf6eac2f078ff9a95cc3599926aca824d541c650f18a66) @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.
Affected software
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- MAL-2026-13861
- Osv Schema Version
- 1.7.4
- Aliases
- []
- Ecosystems
- ["npm"]
- Database Specific Severity
- null
- Cvss Version
- null
Threat ID: 6a7c9b54bf8831d539cde051
Added to database: 08/12/2026, 16:12:04 UTC
Last updated: 08/12/2026, 16:12:04 UTC
Views: 1
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
External Links
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.