Malicious code in @years18/n8n-nodes-utils-helper-s (npm)
The npm package @years18/n8n-nodes-utils-helper-s contained malicious code in its postinstall script that downloads and executes DDoS tools, collects system information, and exfiltrates data to a remote server. The package name mimics legitimate n8n community node packages.
- Disclosed
- Last updated
- Blast radius
- Any developer or system that installed the malicious package during its availability on npm.
- Ecosystems
- Attack vectors
- Affected entities
- @years18/n8n-nodes-utils-helper-sMalicious npm package mimicking legitimate n8n community node packages
The npm package @years18/n8n-nodes-utils-helper-s was published with malicious code embedded in its postinstall lifecycle script. The package name was designed to mimic legitimate n8n community node packages, representing a typosquatting attack.
Upon installation, the postinstall script downloads two tarballs (mhddos.tgz and pyroxy.tgz) from jasabersama.id over HTTPS with TLS verification disabled (rejectUnauthorized:false). These archives are extracted to /tmp and into the Python user site-packages directory. The script then pip-installs a fixed dependency set with the --break-system-packages flag and immediately executes python3 start.py from the extracted mhddos directory.
In parallel, the malicious code collects system information including the output of id and hostname commands, along with install-progress markers. This data is base64-encoded and exfiltrated to https://jasabersama.id/portfolio-data.php as a query-string parameter using a fixed key S7k9xQ2mZj. The payload URL is staged under a .theme-backup/dl/ path on a domain unrelated to the package's declared purpose.
The package's n8n node file is a non-functional stub; all actual functionality is contained in the malicious postinstall script. This incident was identified and credited to the OpenSSF malicious-packages repository.
Indicators of compromise
- Packages
- @years18/n8n-nodes-utils-helper-s
- Domains
- jasabersama.id
Remediation
- Immediately uninstall @years18/n8n-nodes-utils-helper-s from all systems
- Audit npm install logs to identify when the package was installed
- Scan affected systems for the presence of mhddos and pyroxy tools in /tmp and Python site-packages
- Review system logs for suspicious Python process execution and outbound connections to jasabersama.id
- Check for unauthorized network activity or DDoS tool execution on affected systems
- Verify system integrity and check for any persistence mechanisms left by the malicious code
- Use legitimate n8n community node packages from verified sources only
- Consider implementing npm package verification and scanning in your CI/CD pipeline
Sources
- GitHub Advisory GHSA-jj25-9gc3-x3j5 · GitHub Advisory Database
Cite this entry
"Malicious code in @years18/n8n-nodes-utils-helper-s (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-s-npm-1k24do
Suggest a correction
Found an error or have a newer source? Corrections to factual errors take priority over new entries.
Related incidents
- resolvedcritical
Malicious code in depcruise-wrap-stream-in-html (npm)
depcruise-wrap-stream-in-html@99.9.1 is a malicious npm package that mimics an internal helper of dependency-cruiser. It is a hollow package that downloads and executes arbitrary code from a Google Cloud Storage bucket during installation.
npmCompromised packageDependency confusionTyposquatting - resolvedcritical
Malicious code in akamai-sensor (npm)
A malicious npm package named akamai-sensor impersonated Akamai's legitimate sensor_data anti-bot SDK. The package contained hidden JavaScript code concealed using invisible Unicode characters and implemented a dynamic command-and-control channel via a Google Calendar dead-drop, enabling arbitrary code execution on installation.
npmCompromised packageTyposquatting - resolvedcritical
Malicious code in @finaxis/common-js (npm)
The npm package @finaxis/common-js was published with a README and keywords copied from lodash v4.18.1, but contained a heavily obfuscated Xelis (XEL) proof-of-work cryptominer instead of lodash functionality. Consumers installing this package would unknowingly run a covert CPU/GPU miner on their systems.
npmCompromised packageTyposquatting - containedcritical
Malicious code in axios-fast (npm)
axios-fast@1.0.1 on npm contains malicious code that exfiltrates environment variables (including AWS credentials, NPM tokens, and GitHub tokens) to an attacker-controlled webhook during package installation. The package typosquats the legitimate axios HTTP client library.
npmCompromised packageTyposquatting