Malicious code in @years18/n8n-nodes-utils-helper-r (npm)
The npm package @years18/n8n-nodes-utils-helper-r contained a malicious postinstall script that downloads and executes the PyRoxy/MHDDOS DDoS attack framework, collects system information, and exfiltrates it to a remote server.
- Disclosed
- Last updated
- Blast radius
- Any developer or system installing @years18/n8n-nodes-utils-helper-r via npm
- Ecosystems
- Attack vectors
- Affected entities
- @years18/n8n-nodes-utils-helper-rnpm package containing malicious postinstall script
The npm package @years18/n8n-nodes-utils-helper-r, presented as an n8n community utility node, shipped with a malicious postinstall script executed during npm install. The script downloads a tarball from https://jasabersama.id/assets/cache/.theme-backup/dl/pyroxy-full.tgz with TLS certificate verification disabled and extracts it into the Python site-packages directory.\n\nThe postinstall script then executes python3 start.py from /tmp/mhddos, deploying the PyRoxy/MHDDOS DDoS attack framework. Additionally, the script collects system information by executing id and hostname commands, base64-encodes the output, and exfiltrates it via HTTPS GET request to jasabersama.id/portfolio-data.php with a hardcoded key parameter (also with certificate verification disabled).\n\nThe malicious package was identified by Amazon Inspector and credited to the OpenSSF malicious-packages repository. The incident represents a supply chain compromise where a package masquerading as legitimate development tooling delivered offensive DDoS infrastructure to unsuspecting users.
Indicators of compromise
- Packages
- @years18/n8n-nodes-utils-helper-r
- Domains
- jasabersama.id
Remediation
- Immediately uninstall @years18/n8n-nodes-utils-helper-r from all systems
- Audit npm install logs and package-lock.json files to identify affected installations
- Inspect Python site-packages directories for unexpected PyRoxy/MHDDOS files, particularly in /tmp/mhddos
- Review network logs for outbound HTTPS connections to jasabersama.id
- Regenerate credentials and SSH keys on any system that may have installed this package
- Monitor affected systems for signs of DDoS attack framework activity
- Use npm audit to check for this package in dependency trees
Sources
- GitHub Advisory GHSA-778r-j46v-qgf3 · GitHub Advisory Database
Cite this entry
"Malicious code in @years18/n8n-nodes-utils-helper-r (npm)." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed August 12, 2026; last updated August 12, 2026. https://supplychainattack.org/incident/malicious-code-in-years18-n8n-nodes-utils-helper-r-npm-1iist2
Suggest a correction
Found an error or have a newer source? Corrections to factual errors take priority over new entries.
Related incidents
- containedcritical
Malicious code in pfp-forms-sme-loan (npm)
The npm package pfp-forms-sme-loan contains malicious code that executes a hidden loader on import, downloading and running platform-specific native payloads from attacker-controlled Cloudflare Workers hosts or reconstructing them via DNS TXT records under well1.site. Any system that imported this package should be considered compromised.
npmCompromised packageMalicious commit - resolvedcritical
Malicious code in epic-common-node (npm)
The npm package epic-common-node was found to contain malicious code. The package has been identified and reported through GitHub Security Advisory GHSA-m36g-mhjr-ww2c.
npmCompromised package - resolvedcritical
Malicious code in epic-sso (npm)
The npm package epic-sso was found to contain malicious code. The package was identified by Amazon Inspector and reported through the OpenSSF malicious packages database.
npmCompromised package - containedcritical
Malicious code in checkout-desktop-total (npm)
The npm package checkout-desktop-total contained malicious code that executes a hidden loader on import, downloading and running platform-specific native payloads from attacker-controlled Cloudflare Workers hosts or reconstructing them via DNS TXT records under wel1.ru. Any system that imported this package should be considered compromised.
npmCompromised package