MAL-2026-13868 Malicious code in @years18/n8n-nodes-utils-helper-x (npm)
Malicious package
Published
MAL-2026-13868 is a malicious package: @years18/n8n-nodes-utils-helper-x (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-13868/ (Markdown: https://insights.sbomify.com/MAL-2026-13868/index.md)
- Package
- @years18/n8n-nodes-utils-helper-x
- Registry
- npm
What is MAL-2026-13868?
MAL-2026-13868 is a malicious package in @years18/n8n-nodes-utils-helper-x, published on 12 Aug 2026.
Official description
Package presents itself as an n8n utility helper but ships a 213-byte stub node and a hostile postinstall (
node callback.js). On npm install, callback.js fetches two tarballs (impacket.tgz, pyroxy.tgz) over HTTPS with TLS verification disabled from jasabersama.id/assets/cache/.theme-backup/dl/, extracts them into the installer's Python user site-packages so any subsequent Python import runs attacker-controlled code, and probes /tmp/mhddos/start.py (MHDDoS DDoS tooling). The same script collects id and hostname command output plus install-step status, base64-encodes the buffer, and sends it via HTTPS GET to https://jasabersama.id/portfolio-data.php as a URL parameter, indexing compromised hosts. The declared package purpose does not match the shipped behavior; the host is publisher-mismatched and TLS verification is disabled.What should I do about MAL-2026-13868?
Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.