# MAL-2026-6457: Malicious code in subsearch (npm)


- **Type:** Malicious package
- **Package:** `subsearch` (npm)
- **Published:** 25 Jun 2026
- **Also known as:** GHSA-45mm-476v-v2pf

## What is MAL-2026-6457?

MAL-2026-6457 is a malicious package in subsearch, published on 25 Jun 2026. 

### Official description

The package's main entry `index.js` is the only file of substance and is wrapped in obfuscator.io string-array + RC4 obfuscation that hides every literal (module names, URL octets, exec arguments). On require(), the deobfuscated code assembles a bare-IP HTTP URL by concatenating four octets via `.concat('.')`, performs an HTTP GET, writes the response body into `os.tmpdir()` via `fs.writeFileSync(path.join(os.tmpdir(), <name>), I.data, {flag:'w+'})`, and immediately executes the dropped file with `child_process.exec(..., {windowsHide:true, cwd: os.tmpdir()})`. `process.on('uncaughtException',...)` is registered to suppress errors. `package.json` has empty description, empty author, no repository, no homepage — the package advertises no functionality; its only effect on import is the dropper. The bare-IP destination has no TLS, no pinning, and no signature verification, so the attacker can swap the executed payload at any 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-6457?

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

## Sources

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

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