Malicious code in @years18/n8n-nodes-utils-helper-v (npm)
The npm package @years18/n8n-nodes-utils-helper-v contained malicious code that executed reconnaissance and staged DDoS/network-attack tooling on installation. The package masqueraded as a legitimate n8n community node while its postinstall script exfiltrated host identifiers and installed offensive tools.
- Disclosed
- Last updated
- Blast radius
- Any developer or system that installed the malicious package via npm
- Ecosystems
- Attack vectors
- Affected entities
- @years18/n8n-nodes-utils-helper-vMalicious npm package masquerading as n8n community node
The npm package @years18/n8n-nodes-utils-helper-v was a malicious package that masqueraded as an n8n community node. The package contained a postinstall script that executed upon installation, performing multiple malicious actions.
Upon installation, the postinstall script collected host identity information (user ID and hostname) via callback.js, base64-encoded the data, and exfiltrated it to https://jasabersama.id/portfolio-data.php with TLS verification disabled. The same script installed the impacket network-attack library via pip with the --break-system-packages flag, probed PyRoxy, and attempted to execute /tmp/mhddos/start.py (MHDDoS), staging DDoS and network-attack capabilities on the installer's machine.
The package was identified and credited to the OpenSSF malicious-packages repository (MAL-2026-13866). This represents a supply chain attack combining typosquatting (mimicking legitimate n8n nodes) with a compromised package delivery mechanism.
Indicators of compromise
- Packages
- @years18/n8n-nodes-utils-helper-v
- Domains
- jasabersama.id
Remediation
- Immediately uninstall @years18/n8n-nodes-utils-helper-v from all systems
- Audit npm install logs to identify all systems that installed this package
- Revoke any credentials or tokens that may have been exposed on affected systems
- Scan affected systems for the presence of /tmp/mhddos/ and impacket library installations
- Monitor affected systems for unexpected network connections and DDoS activity
- Review network logs for connections to jasabersama.id
- Use npm audit to identify and remove the malicious package from dependency trees
- Verify the legitimacy of n8n community nodes before installation by checking official n8n repositories
Sources
- GitHub Advisory GHSA-5wrc-8g4h-mjrw · GitHub Advisory Database
Cite this entry
"Malicious code in @years18/n8n-nodes-utils-helper-v (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-v-npm-1qh5ya
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 @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 - 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 wct-st (npm)
The npm package wct-st contained malicious code in its postinstall lifecycle script that collected and exfiltrated host identifiers to a remote endpoint. The package name resembles the deprecated web-component-tester, consistent with a typosquatting attack.
npmCompromised packageTyposquatting