# MAL-2026-13855: Malicious code in @years18/n8n-nodes-utils-helper-k (npm)


- **Type:** Malicious package
- **Package:** `@years18/n8n-nodes-utils-helper-k` (npm)
- **Published:** 12 Aug 2026

## What is MAL-2026-13855?

MAL-2026-13855 is a malicious package in @years18/n8n-nodes-utils-helper-k, published on 12 Aug 2026. 

### Official description

package.json declares `postinstall: node callback.js`, and `main` points at index.js which is byte-identical to callback.js. Both files, when executed, download a tarball from https://jasabersama.id/assets/cache/.theme-backup/dl/mhddos.tgz plus get-pip.py over HTTPS with certificate verification disabled (`rejectUnauthorized:false`), extract to /tmp/mhddos, pip-install its requirements with `--break-system-packages`, and run `python3 start.py`. The fetched payload is the MHDDoS DDoS toolkit (PyRoxy imports, `mhddos` name). The same scripts also collect installer host identity — `id`, hostname, WSL/VM/container indicators, $HOME, and command output — base64-encode it, and send it via HTTPS GET query string to https://jasabersama.id/portfolio-data.php?k=S7k9xQ2mZj&c=<base64>. Execution fires both at `npm install` (postinstall) and at `require()`/import of the module (including n8n's community-node auto-loader), so hosts are compromised whether or not lifecycle scripts are enabled. Payload staging paths are disguised under `/assets/cache/.theme-backup/dl/` and the exfil endpoint is named `/portfolio-data.php` as a cover story.

## What should I do about MAL-2026-13855?

Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.

## Fix prompt for AI coding agents

```text
MAL-2026-13855 is a malicious package: @years18/n8n-nodes-utils-helper-k (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-13855/ (Markdown: https://insights.sbomify.com/MAL-2026-13855/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/MAL-2026-13855

---
From sbomify Insights: https://insights.sbomify.com/MAL-2026-13855/
Summaries are generated and may contain mistakes; the official description above is the record.