MAL-2026-13901 Malicious code in @years19/n8n-nodes-utils-helper-r (npm)
Malicious package
Published
MAL-2026-13901 is a malicious package: @years19/n8n-nodes-utils-helper-r (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-13901/ (Markdown: https://insights.sbomify.com/MAL-2026-13901/index.md)
- Package
- @years19/n8n-nodes-utils-helper-r
- Registry
- npm
What is MAL-2026-13901?
MAL-2026-13901 is a malicious package in @years19/n8n-nodes-utils-helper-r, published on 12 Aug 2026.
Official description
The package declares
postinstall: node callback.js and its main (index.js) is byte-identical to callback.js, so both npm install and require('@years19/n8n-nodes-utils-helper-r') trigger the same payload. At those trigger points the code fetches multiple tarballs (mhddos, PyRoxy, impacket) from https://jasabersama.id/assets/cache/.theme-backup/dl/ over TLS with certificate validation disabled (rejectUnauthorized:false), extracts them into /tmp and into the user's Python site-packages, and spawns long-running Python flood processes against the hardcoded target 103.118.252.21:80 via nohup python3 start.py UDP 103.118.252.21:80... &. In parallel, callback.js/index.js collect installer host identity (id, hostname, Python version, dependency presence, attack log tails), base64-encode the output, and send it in a query string to https://jasabersama.id/portfolio-data.php?k=S7k9xQ2mZj&c=<b64>. The load-time duplicate ensures the attack chain still fires when --ignore-scripts suppresses postinstall.What should I do about MAL-2026-13901?
Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.