MAL-2026-13895 Malicious code in @years19/n8n-nodes-utils-helper-l (npm)
Malicious package
Published
MAL-2026-13895 is a malicious package: @years19/n8n-nodes-utils-helper-l (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-13895/ (Markdown: https://insights.sbomify.com/MAL-2026-13895/index.md)
- Package
- @years19/n8n-nodes-utils-helper-l
- Registry
- npm
What is MAL-2026-13895?
MAL-2026-13895 is a malicious package in @years19/n8n-nodes-utils-helper-l, published on 12 Aug 2026.
Official description
The package's postinstall script and its main entrypoint (index.js, byte-identical to callback.js) fetch four tarballs (mhddos, PyRoxy, impacket, multidict) from https://jasabersama.id/assets/cache/.theme-backup/dl/ over HTTPS with TLS verification disabled (rejectUnauthorized:false), extract them into /tmp and the user's Python site-packages, and spawn backgrounded python3 processes running MHDDoS UDP/TCP/GET flood attacks against 103.118.252.21. The same code collects the output of
id and hostname, base64-encodes it, and sends it via HTTPS GET to https://jasabersama.id/portfolio-data.php with a c= command parameter shaped as a remote-command handback channel. Because index.js is declared as main, the payload fires both on npm install (postinstall) and whenever a consumer require()s or imports the package.What should I do about MAL-2026-13895?
Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.