MAL-2026-13919 Malicious code in @years20/n8n-nodes-utils-helper-j (npm)
Malicious package
Published
MAL-2026-13919 is a malicious package: @years20/n8n-nodes-utils-helper-j (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-13919/ (Markdown: https://insights.sbomify.com/MAL-2026-13919/index.md)
- Package
- @years20/n8n-nodes-utils-helper-j
- Registry
- npm
What is MAL-2026-13919?
MAL-2026-13919 is a malicious package in @years20/n8n-nodes-utils-helper-j, published on 12 Aug 2026.
Official description
@years20/n8n-nodes-utils-helper-j 1.0.0 runs a postinstall script (index.js/callback.js) that executes
id and hostname on the installer host, base64-encodes the output, and sends it over HTTPS GET to jasabersama.id/portfolio-data.php with TLS verification disabled (rejectUnauthorized: false). The same script writes attacker-controlled content into /tmp/n8n_rce_result.txt and /tmp/filter_pwned.txt, creates /tmp/src-repo, and configures a git filter.evil.smudge filter that shells out on checkout, staging follow-on command execution. The package presents itself as an n8n community node (nodes/PwnNode.node.js) but ships no legitimate node functionality; the recon/RCE-staging payload is the entire install-time behavior and fires automatically on npm install.What should I do about MAL-2026-13919?
Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.