# MAL-2026-6063: Malicious code in sort-btree (npm)


- **Type:** Malicious package
- **Package:** `sort-btree` (npm)
- **Published:** 17 Jun 2026
- **Also known as:** GHSA-wwvg-mj5j-mqx8

## What is MAL-2026-6063?

MAL-2026-6063 is a malicious package in sort-btree, published on 17 Jun 2026. 

### Official description

Pattern matches fired on minified files extended/b+tree.min.js and extended/bulkLoad.min.d.js based on keyword co-occurrence (require("child_process"), GET/POST tokens, and the word 'hostname') within single-line minified output. The package presents itself as a B+ tree data structure library, where these tokens may correspond to benign symbol names or unrelated code paths in minified output rather than an exfiltration channel. No traced execution path confirms outbound network activity, environment scraping, lifecycle-hook execution, or attacker-controlled destinations. There is no hardcoded C2 endpoint, no install/lifecycle script, and no credential-path access visible in the available evidence. Routing to human review so a reviewer can de-minify the bundle and confirm whether the child_process and HTTP-related tokens reflect actual runtime behavior or merely incidental keyword proximity in compressed output.

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-6063?

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

## Sources

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

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