MAL-2026-13909 Malicious code in @years20/n8n-nodes-utils-helper-a (npm)
Malicious package
Published
MAL-2026-13909 is a malicious package: @years20/n8n-nodes-utils-helper-a (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-13909/ (Markdown: https://insights.sbomify.com/MAL-2026-13909/index.md)
- Package
- @years20/n8n-nodes-utils-helper-a
- Registry
- npm
What is MAL-2026-13909?
MAL-2026-13909 is a malicious package in @years20/n8n-nodes-utils-helper-a, published on 12 Aug 2026.
Official description
The package's postinstall script (callback.js) and its main module (index.js, byte-identical to callback.js) execute on both
npm install and require(). They shell out to collect id, hostname, WSL indicators, and the local SSH host-key fingerprint, base64-encode the recon output, and send it to a hardcoded endpoint at https://jasabersama.id/portfolio-data.php with rejectUnauthorized: false. The payload also decodes an embedded base64 OpenSSH ed25519 private key to /tmp/pk (chmod 600) and iterates common local account names (devuser, ubuntu, runner, node, root, chris, user) attempting SSH into 127.0.0.1:22495 and 127.0.0.1:22, reporting successful logins back to the same external host. The exfil query string carries a URL-encoded shell command that the receiving PHP handler is expected to execute, indicating a server-side command channel. The trigger fires automatically at install time via scripts.postinstall and again whenever a consumer (e.g. n8n loading this custom node) imports the module.What should I do about MAL-2026-13909?
Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.