Which versions of bs58-11 are malicious?

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

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

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

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

Yes — bs58-11 is associated with the GHSA-mw39-7442-3p8m, IN-MAL-2026-017436 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-11 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-11 (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-11 across your stack and pipelines.

Malicious package

bs58-11npm

bs58-11 is a confirmed malicious npm package (MAL-2026-13758) 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-11 (npm)

MAL-2026-13758

Immediate action

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

npm uninstall bs58-11

What this malware does

Package bs58-11 is published under a name that resembles the popular bs58 module. Its README self-identifies as bs58 and instructs npm i --save bs58, while package.json declares the name as bs58-11. The tarball contains only a two-line wrapper (index.cjs) that requires base65-11x — a name resembling the legitimate base-x package — and immediately invokes its default export at module load. The wrapper itself contains no exfiltration, credential access, install-time fetch-and-execute, silent-relay, or backdoor code. Any behavior beyond base-x-style alphabet decoding depends on the content of the base65-11x dependency, which is not part of this tarball.

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)

8a9f90466ed9f42f4891cc53d4a86bd0dc7477c72e007decc817a8dcc7648093

af29bcf6fea2d386f8beb757fa38bac5f1cc6dbae984795f5fd1f4356afd83f7

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-11 (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-11 across your stack and pipelines.
If you installed it — respond
bs58-11 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-11 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-11 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-11 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-mw39-7442-3p8mIN-MAL-2026-017436

References

Credits

Amazon Inspector · finder

Detect & block this

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