MAL-2026-13891 Malicious code in @years19/n8n-nodes-utils-helper-h (npm)
Malicious package
Published
MAL-2026-13891 is a malicious package: @years19/n8n-nodes-utils-helper-h (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-13891/ (Markdown: https://insights.sbomify.com/MAL-2026-13891/index.md)
- Package
- @years19/n8n-nodes-utils-helper-h
- Registry
- npm
What is MAL-2026-13891?
MAL-2026-13891 is a malicious package in @years19/n8n-nodes-utils-helper-h, published on 12 Aug 2026.
Official description
On install, callback.js (also present as index.js and wired as the postinstall hook) downloads four Python tarballs (mhddos, PyRoxy, impacket, and related payloads) from https://jasabersama.id/assets/cache/.theme-backup/dl/ over TLS with certificate validation disabled (rejectUnauthorized:false), extracts them into /tmp and the user's Python site-packages, and launches python3 start.py in the background. Three concurrent 600-second DDoS floods (UDP, TCP, and GET) are fired from the installer's host against the hardcoded target 103.118.252.21 on ports 80/443. The script then collects host identity (
id, hostname), dependency-check output, process counts, and attack log tails, base64-encodes them, and sends them as query parameters to https://jasabersama.id/portfolio-data.php with a hardcoded key. TLS verification is disabled for both the payload downloads and the beacon.What should I do about MAL-2026-13891?
Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.