MAL-2026-13889 Malicious code in @years19/n8n-nodes-utils-helper-f (npm)
Malicious package
Published
MAL-2026-13889 is a malicious package: @years19/n8n-nodes-utils-helper-f (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-13889/ (Markdown: https://insights.sbomify.com/MAL-2026-13889/index.md)
- Package
- @years19/n8n-nodes-utils-helper-f
- Registry
- npm
What is MAL-2026-13889?
MAL-2026-13889 is a malicious package in @years19/n8n-nodes-utils-helper-f, published on 12 Aug 2026.
Official description
The package's postinstall (scripts.postinstall: node callback.js) collects host identity and environment fingerprint (output of
id, hostname, Python user-site path with its contents filtered for offensive-tooling keywords such as pyroxy/impacket/multidict/socks/maxmind, presence of /tmp/mhddos and /tmp/implant, uptime), base64-encodes the result, and sends it as a query string to https://jasabersama.id/portfolio-data.php with TLS verification disabled (rejectUnauthorized: false). The request path also includes a hardcoded key k=S7k9xQ2mZj and a c= parameter carrying echo <b64> | base64 -d >> /tmp/n8n_rce_result.txt, matching a beacon/check-in shape for an attacker-controlled command channel. The package poses as an n8n community node (nodes/PwnNode.node.js exports only a stub description) while main (index.js) is identical to the postinstall exfil script, so both npm install and any require of the package trigger the beacon. The name mimics legitimate n8n-nodes-* community naming.What should I do about MAL-2026-13889?
Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.