MAL-2026-13907 Malicious code in @years19/n8n-nodes-utils-helper-x (npm)
Malicious package
Published
MAL-2026-13907 is a malicious package: @years19/n8n-nodes-utils-helper-x (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-13907/ (Markdown: https://insights.sbomify.com/MAL-2026-13907/index.md)
- Package
- @years19/n8n-nodes-utils-helper-x
- Registry
- npm
What is MAL-2026-13907?
MAL-2026-13907 is a malicious package in @years19/n8n-nodes-utils-helper-x, published on 12 Aug 2026.
Official description
The package's postinstall hook runs node callback.js, and package.json declares main=index.js which is byte-identical to callback.js, so both npm install and require() of the package execute the same payload. The payload writes /tmp/attack2.py — a threaded UDP/TCP flood loop targeting 103.118.252.21 for 900 seconds — and launches it via
nohup python3 /tmp/attack2.py &, weaponizing the installer's host and IP as a DDoS bot. In parallel, it collects the output of id, hostname, a process check and /proc/loadavg, base64-encodes it, and sends it over HTTPS GET to jasabersama.id/portfolio-data.php with TLS verification disabled (rejectUnauthorized:false). The package is presented as an n8n utility helper but ships no such functionality; its only observable behavior is the DDoS launcher and host-identity beacon.What should I do about MAL-2026-13907?
Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.