MAL-2026-13867 Malicious code in @years18/n8n-nodes-utils-helper-w (npm)
Malicious package
Published
MAL-2026-13867 is a malicious package: @years18/n8n-nodes-utils-helper-w (npm). Every version was published to cause harm.
Task:
1. Search this repository's dependency manifests and lockfiles for the package, including transitive dependencies.
2. If it is present, remove it, regenerate the lockfile with the project's package manager, and replace whatever it was used for.
3. List any CI runners, developer machines or containers that installed it, so their secrets can be rotated.
4. If the package is not used anywhere, say so and change nothing.
Reference: https://insights.sbomify.com/MAL-2026-13867/ (Markdown: https://insights.sbomify.com/MAL-2026-13867/index.md)
- Package
- @years18/n8n-nodes-utils-helper-w
- Registry
- npm
What is MAL-2026-13867?
MAL-2026-13867 is a malicious package in @years18/n8n-nodes-utils-helper-w, published on 12 Aug 2026.
Official description
This package presents itself as an n8n workflow helper but ships a near-empty node stub (nodes/PwnNode.node.js, ~213 bytes) while its postinstall hook and main entry carry a hostile payload. package.json declares postinstall: node callback.js, and index.js is a byte-identical copy of callback.js, so both
npm install and require() execute the same code. The payload runs id and hostname, probes for Python packages, executes a staged tool at /tmp/mhddos/start.py (the MHDDoS attack toolkit), base64-encodes the aggregated output, and sends it as a URL query parameter to https://jasabersama.id/portfolio-data.php over HTTPS with TLS verification disabled (rejectUnauthorized:false). It also runs python3 -m pip install --quiet --break-system-packages impacket, mutating the installer's system Python environment, and executes attacker-staged code from /tmp. The mismatch between the advertised n8n-helper purpose and the shipped functionality — plus duplication of the payload across both auto-executed surfaces — indicates the declared purpose is a cover for the attack.What should I do about MAL-2026-13867?
Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.