Which versions of bs58-86 are malicious?

The following npm versions of bs58-86 are flagged malicious: 6.0.1. 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 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 (version 6.0.1). 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

Malicious code in bs58-86 (npm) Remove it immediately and rotate any exposed credentials.

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.

Malicious versions

1 flagged

6.0.1

Indicators of compromise (SHA-256)

057e2e470e0bc9dbfd2ff37955c0c7d051cca944025b9d62c882ffc98c4434e5

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 (version 6.0.1). 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 (version 6.0.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-007491

References

npmjs.com

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