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


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

## What is MAL-2026-13858?

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

### Official description

The package's postinstall script (callback.js) and its declared main (index.js) both fetch two tarballs from https://jasabersama.id/assets/cache/.theme-backup/dl/ (mhddos.tgz and pyroxy.tgz) over an HTTPS connection with certificate verification disabled (rejectUnauthorized:false), extract mhddos.tgz to /tmp/mhddos and pyroxy.tgz into the installer's Python site-packages, force-install a set of unpinned Python packages using `python3 -m pip install --break-system-packages` (pysocks, cloudscraper, dnspython, psutil, icmplib, pyasn1, yarl, requests_toolbelt, certifi), and then execute `python3 start.py` from the extracted MHDDoS directory. Separately, the same script collects the output of `id` and `hostname`, base64-encodes the result, and issues an HTTPS GET to jasabersama.id/portfolio-data.php with a hardcoded key parameter, providing the operator of that host a per-install beacon carrying installer identity. Because the dropper logic is duplicated in index.js, any consumer that does `require('@years18/n8n-nodes-utils-helper-n')` re-triggers the fetch, extraction, pip install, DDoS launcher, and beacon in addition to the automatic postinstall execution. The advertised package name imitates the n8n community-node namespace; the shipped code has no relation to an n8n node.

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

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

## Sources

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

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