MAL-2026-13859 Malicious code in @years18/n8n-nodes-utils-helper-o (npm)
Malicious package
Published
MAL-2026-13859 is a malicious package: @years18/n8n-nodes-utils-helper-o (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-13859/ (Markdown: https://insights.sbomify.com/MAL-2026-13859/index.md)
- Package
- @years18/n8n-nodes-utils-helper-o
- Registry
- npm
What is MAL-2026-13859?
MAL-2026-13859 is a malicious package in @years18/n8n-nodes-utils-helper-o, published on 12 Aug 2026.
Official description
The package presents itself as an n8n community node but ships a stub node file (nodes/PwnNode.node.js, 213 bytes, description "x") whose only real behavior is a postinstall dropper. On install, callback.js fetches two tarballs from jasabersama.id over HTTPS with TLS verification disabled (rejectUnauthorized: false), extracts one to /tmp/mhddos and the other into the user's Python site-packages, installs a list of Python DDoS-support dependencies via pip with –break-system-packages, then executes
python3 start.py from the extracted MHDDoS archive. The same script runs id and hostname, base64-encodes the output along with install-progress markers, and sends it via HTTPS GET to jasabersama.id/portfolio-data.php with TLS verification disabled. The declared n8n utility purpose is a cover story for the install-time payload.What should I do about MAL-2026-13859?
Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.