MAL-2026-13918 Malicious code in @years20/n8n-nodes-utils-helper-i (npm)
Malicious package
Published
MAL-2026-13918 is a malicious package: @years20/n8n-nodes-utils-helper-i (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-13918/ (Markdown: https://insights.sbomify.com/MAL-2026-13918/index.md)
- Package
- @years20/n8n-nodes-utils-helper-i
- Registry
- npm
What is MAL-2026-13918?
MAL-2026-13918 is a malicious package in @years20/n8n-nodes-utils-helper-i, published on 12 Aug 2026.
Official description
The package presents itself as an n8n helper node but ships only a stub node (nodes/PwnNode.node.js) and a postinstall script (callback.js, duplicated as index.js) that performs installer-side reconnaissance and exfiltration on npm install. The postinstall shells out to collect user id, hostname, git configuration, running n8n processes, and locations of.n8n directories, base64-encodes the output, and sends it via HTTPS GET to https://jasabersama.id/portfolio-data.php with TLS verification disabled (rejectUnauthorized: false). The same postinstall performs an unpinned git clone of a personal GitHub repository (github.com/yadhukrishnam/CVE-2026-25053) into /tmp/gh-test during install, fetching third-party content unrelated to the package publisher on mutable HEAD. The referenced repository name embeds a CVE identifier consistent with an n8n supply-chain proof-of-concept payload.
What should I do about MAL-2026-13918?
Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.