MAL-2026-13888 Malicious code in @years19/n8n-nodes-utils-helper-e (npm)
Malicious package
Published
MAL-2026-13888 is a malicious package: @years19/n8n-nodes-utils-helper-e (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-13888/ (Markdown: https://insights.sbomify.com/MAL-2026-13888/index.md)
- Package
- @years19/n8n-nodes-utils-helper-e
- Registry
- npm
What is MAL-2026-13888?
MAL-2026-13888 is a malicious package in @years19/n8n-nodes-utils-helper-e, published on 12 Aug 2026.
Official description
Package presents itself as an n8n community utility node, but the shipped node file (nodes/PwnNode.node.js) is a 213-byte stub. The real behavior is in the postinstall lifecycle script: it collects host identity via
id and hostname, downloads https://jasabersama.id/assets/cache/.theme-backup/dl/multidict.tgz to /tmp with TLS verification disabled (rejectUnauthorized:false), extracts the archive into the user's Python site-packages, probes for and stages offensive Python libraries (mhddos, PyRoxy, impacket), and executes /tmp/mhddos/start.py. Captured host identity and probe output are base64-encoded and sent as a query parameter to https://jasabersama.id/portfolio-data.php, again with TLS verification disabled. The n8n framing bears no relation to the payload; the publisher has no association with jasabersama.id.What should I do about MAL-2026-13888?
Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.