MAL-2026-13863 Malicious code in @years18/n8n-nodes-utils-helper-s (npm)
Malicious package
Published
MAL-2026-13863 is a malicious package: @years18/n8n-nodes-utils-helper-s (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-13863/ (Markdown: https://insights.sbomify.com/MAL-2026-13863/index.md)
- Package
- @years18/n8n-nodes-utils-helper-s
- Registry
- npm
What is MAL-2026-13863?
MAL-2026-13863 is a malicious package in @years18/n8n-nodes-utils-helper-s, published on 12 Aug 2026.
Official description
The package's postinstall lifecycle script downloads two tarballs (mhddos.tgz, pyroxy.tgz) from jasabersama.id over an HTTPS connection with TLS verification disabled (rejectUnauthorized:false), extracts them to /tmp and into the Python user site-packages, pip-installs a fixed dependency set with –break-system-packages, and immediately runs
python3 start.py from the extracted mhddos directory. In parallel, it collects the output of id and hostname plus install-progress markers, base64-encodes them, and sends them as a query-string parameter to https://jasabersama.id/portfolio-data.php with a fixed key S7k9xQ2mZj. The payload URL is staged under a .theme-backup/dl/ cover-story path on a domain unrelated to the package's declared purpose, and the package's n8n node file is a stub — the sole functional code is the malicious postinstall. The name mimics legitimate n8n community node packages.What should I do about MAL-2026-13863?
Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.