Which versions of bs58-88 are malicious?

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

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

bs58-88 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 bs58-88 — how do I know if it already compromised me?

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

Yes — bs58-88 is associated with the GHSA-qj7h-vp7h-8v85, IN-MAL-2026-012928 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-88 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-88 (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-88 across your stack and pipelines.

Malicious package

bs58-88npm

bs58-88 is a confirmed malicious npm package (MAL-2026-11023) that steals credentials and exfiltrates sensitive data (malicious version 6.0.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in bs58-88 (npm)

MAL-2026-11023

Immediate action

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

npm uninstall bs58-88

What this malware does

Package bs58-88 mimics the popular bs58 base58 encoder: README, keywords, and repository URL match the real bs58, and index.cjs re-exports functionality via require("base65-85x"). The sole runtime dependency base65-85x is itself a name that resembles the legitimate base-x package. The package under review does not contain traced installer-harm behavior (no exfiltration, no install-time fetch-and-execute, no credential access, no lifecycle scripts observed), so the concern is name-confusion plus a look-alike transitive rather than a demonstrated payload in this artifact. Whether base65-85x is itself malicious was not established here; a human reviewer should assess both the name-similarity judgment against bs58/base-x and the trust of the base65-85x dependency before publishing a public advisory.

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

1 flagged

6.0.1

Indicators of compromise (SHA-256)

2e251130fcb84c2b20ede3b09d95f501bd3b593c051cf0f95d6beba9b11949a2

b6d1dec3ae934b73d28ddd4c002cf93f9a9be597731434f5cfead7fdbb11954f

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 bs58-88 (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-88 across your stack and pipelines.
If you installed it — respond
bs58-88 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 bs58-88 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-88 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-88 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

GHSA-qj7h-vp7h-8v85IN-MAL-2026-012928

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks bs58-88-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