Which versions of bs58-86 are malicious?

The following npm versions of bs58-86 are flagged malicious: 6.0.1, 6.0.2. Treat any of these as compromised.

How do I remediate bs58-86 if I installed it?

bs58-86 is a typosquat — you almost certainly intended a legitimately-named package. Remove bs58-86, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.

I already installed bs58-86 — how do I know if it already compromised me?

If bs58-86 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 bs58-86 part of a known attack campaign?

Yes — bs58-86 is associated with the IN-MAL-2026-007491, GHSA-9gvv-wfph-q6rj, IN-MAL-2026-009822 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 bs58-86 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 bs58-86 (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging bs58-86 across your stack and pipelines.

Malicious package

bs58-86npm

bs58-86 is a confirmed malicious npm package (MAL-2026-6448) that typosquats a legitimate package to trick installs (malicious versions 6.0.1, 6.0.2). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in bs58-86 (npm)

MAL-2026-6448

Immediate action

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

npm uninstall bs58-86

What this malware does

Package [email protected] reproduces the name, README, repository URL (cryptocoinjs/bs58), and exported API of the widely-used bs58 base58 encoding library (>10M downloads/week). The only functional code in src/cjs/index.cjs is require('base62-86x')(ALPHABET) — instead of depending on the real base-x package that genuine bs58 uses, this package pulls in base62-86x (declared as ^5.0.4 in package.json dependencies), an unrelated package controlled by a different publisher. All actual base-x implementation runs out of base62-86x, so any developer who installs bs58-86 thinking it is bs58 ends up executing whatever base62-86x ships, at require time. This is the typosquat-plus-dependency-redirect shape: the lure package is a thin shim whose only effect on the installer is to pull in and execute the redirected dependency.

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

6.0.16.0.2

Indicators of compromise (SHA-256)

057e2e470e0bc9dbfd2ff37955c0c7d051cca944025b9d62c882ffc98c4434e5

a08f802970ec2018540c73586abf53983f4038c066307734554eeb2686d71607

a5154a12a69e766d413c5f9498cc217397973b0e38a9b9440fd3e291a64ebe03

Detection & response playbook

Typosquat

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for bs58-86 (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging bs58-86 across your stack and pipelines.
If you installed it — respond
bs58-86 is a typosquat — you almost certainly intended a legitimately-named package. Remove bs58-86, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.
Did it already run?
If bs58-86 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 bs58-86 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. bs58-86 on npm has been identified as a malicious package (versions 6.0.1, 6.0.2 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-007491GHSA-9gvv-wfph-q6rjIN-MAL-2026-009822

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks bs58-86-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database