MAL-2026-13917 Malicious code in @years20/n8n-nodes-utils-helper-h (npm)
Malicious package
Published
MAL-2026-13917 is a malicious package: @years20/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-13917/ (Markdown: https://insights.sbomify.com/MAL-2026-13917/index.md)
- Package
- @years20/n8n-nodes-utils-helper-h
- Registry
- npm
What is MAL-2026-13917?
MAL-2026-13917 is a malicious package in @years20/n8n-nodes-utils-helper-h, published on 12 Aug 2026.
Official description
Package presents itself as an n8n community utility node but ships only a 213-byte no-op node file (nodes/PwnNode.node.js, self-labeled 'Pwn'). The real behavior is in callback.js (invoked via scripts.postinstall and byte-identical to the package's main index.js): it shells out to gather host reconnaissance (id, hostname, git and node versions, n8n install paths, contents of ~/.n8n), base64-encodes the output, and transmits it over HTTPS GET to a hardcoded endpoint at https://jasabersama.id/portfolio-data.php with a fixed key parameter and TLS certificate verification disabled (rejectUnauthorized:false). The URL's
c= parameter smuggles a shell pipeline (echo <base64> | base64 -d >> /tmp/n8n_rce_result.txt) indicative of C2-style tasking. The exfil fires automatically on npm install and again on any require() of the package.What should I do about MAL-2026-13917?
Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.