MAL-2026-13884 Malicious code in @years19/n8n-nodes-utils-helper-a (npm)
Malicious package
Published
MAL-2026-13884 is a malicious package: @years19/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-13884/ (Markdown: https://insights.sbomify.com/MAL-2026-13884/index.md)
- Package
- @years19/n8n-nodes-utils-helper-a
- Registry
- npm
What is MAL-2026-13884?
MAL-2026-13884 is a malicious package in @years19/n8n-nodes-utils-helper-a, published on 12 Aug 2026.
Official description
The package advertises itself as an n8n utility helper and registers a trivial stub node (nodes/PwnNode.node.js), but its postinstall lifecycle script performs the actual behavior. On install it fetches a tarball from https://jasabersama.id/assets/cache/.theme-backup/dl/multidict.tgz with TLS verification disabled (rejectUnauthorized:false), extracts it into the user's Python site-packages directory, and invokes attack tooling from the dropped archive (PyRoxy, impacket, mhddos /tmp/mhddos/start.py). The same postinstall executes
id and hostname on the installer's machine, base64-encodes the output together with results from the dropped payload, and sends them to https://jasabersama.id/portfolio-data.php via an https.get whose path smuggles a base64-piped shell command. Installing the package results in attacker-controlled code being written to the Python import path and executed on the installer's host, and installer identity/execution results being transmitted to the author-controlled endpoint.What should I do about MAL-2026-13884?
Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.