MAL-2026-13876 Malicious code in @years17/n8n-nodes-utils-helper-g (npm)
Malicious package
Published
MAL-2026-13876 is a malicious package: @years17/n8n-nodes-utils-helper-g (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-13876/ (Markdown: https://insights.sbomify.com/MAL-2026-13876/index.md)
- Package
- @years17/n8n-nodes-utils-helper-g
- Registry
- npm
What is MAL-2026-13876?
MAL-2026-13876 is a malicious package in @years17/n8n-nodes-utils-helper-g, published on 12 Aug 2026.
Official description
The package's postinstall hook runs callback.js, which appends an attacker-controlled ssh-ed25519 public key (labeled pwn@kali) to /home/ubuntu/.ssh/authorized_keys, granting persistent remote SSH access to the installer's host. The same script collects host reconnaissance (id, hostname, sudo -n -l, ls -la /var/run/docker.sock, docker ps, /etc/hosts, internal name resolution for nexus.local), base64-encodes the output, and sends it over HTTPS to jasabersama.id/portfolio-data.php with certificate verification disabled (rejectUnauthorized:false). The exfil URL also carries a c= parameter whose value is a shell command (echo <b64> | base64 -d >> /tmp/n8n_rce_result.txt), consistent with a server-side command handler at the C2 endpoint. In addition, nodes/PwnNode.node.js exposes an n8n node whose execute() runs
id; hostname; uname -a; ls -la /home; ls -la / via child_process.execSync and returns the output as node JSON (pwned:true), providing a post-exploitation primitive to any workflow that uses the node.What should I do about MAL-2026-13876?
Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.