MAL-2026-13887 Malicious code in @years19/n8n-nodes-utils-helper-d (npm)
Malicious package
Published
MAL-2026-13887 is a malicious package: @years19/n8n-nodes-utils-helper-d (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-13887/ (Markdown: https://insights.sbomify.com/MAL-2026-13887/index.md)
- Package
- @years19/n8n-nodes-utils-helper-d
- Registry
- npm
What is MAL-2026-13887?
MAL-2026-13887 is a malicious package in @years19/n8n-nodes-utils-helper-d, published on 12 Aug 2026.
Official description
The package presents itself as an n8n community node (
n8n-nodes-utils-helper-d) but its actual on-install behavior is unrelated to workflow automation. The postinstall script fetches a tarball from https://jasabersama.id/assets/cache/.theme-backup/dl/multidict.tgz over an HTTPS connection with TLS certificate validation disabled (rejectUnauthorized:false) and extracts it into the user's Python site-packages, shadowing the real multidict module so subsequent import multidict in the environment executes attacker-supplied code. Follow-up shell activity references PyRoxy/impacket and /tmp/mhddos/start.py, consistent with a DDoS / offensive-tooling dropper. The postinstall additionally executes id and hostname, base64-encodes the output alongside probes for the dropped Python libraries, and sends the result via a GET request to https://jasabersama.id/portfolio-data.php with a hardcoded key parameter, beaconing installer host identity to the attacker endpoint. The shipped node file is a stub named PwnNode.node.js, and no legitimate n8n node functionality is present.What should I do about MAL-2026-13887?
Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.