Which versions of sort-btree are malicious?

The following npm versions of sort-btree are flagged malicious: 2.1.6, 2.2.0. Treat any of these as compromised.

How do I remediate sort-btree if I installed it?

sort-btree is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

I already installed sort-btree — how do I know if it already compromised me?

If sort-btree was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.

Is sort-btree part of a known attack campaign?

Yes — sort-btree is associated with the GHSA-wwvg-mj5j-mqx8, IN-MAL-2026-009175, IN-MAL-2026-009174 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find sort-btree across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for sort-btree (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging sort-btree across your stack and pipelines.

Malicious package

sort-btreenpm

sort-btree is a confirmed malicious npm package (MAL-2026-6063) that steals credentials and exfiltrates sensitive data (malicious versions 2.1.6, 2.2.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in sort-btree (npm)

MAL-2026-6063

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall sort-btree

What this malware does

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.

Malicious versions

2 flagged

2.1.62.2.0

Indicators of compromise (SHA-256)

6c3b0d783c53decf1a240f02276991c7c00a8b72f0d3988a7e86be90464da38d

c21e3fbfbd2c75d226e7f427d760d771d29d6f612eaaa98b5b6daed7bc164035

d75fea163f11c5cbe7c85c1eba35c77e7481658bba381b13fe62e3414f361240

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for sort-btree (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging sort-btree across your stack and pipelines.
If you installed it — respond
sort-btree is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If sort-btree was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks sort-btree before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.

Frequently asked questions

No. sort-btree on npm has been identified as a malicious package (versions 2.1.6, 2.2.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-wwvg-mj5j-mqx8IN-MAL-2026-009175IN-MAL-2026-009174

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks sort-btree-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database