Which versions of node-base58 are malicious?

The following npm versions of node-base58 are flagged malicious: 1.0.1. Treat any of these as compromised.

How do I remediate node-base58 if I installed it?

Remove node-base58 from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

I already installed node-base58 — how do I know if it already compromised me?

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

Yes — node-base58 is associated with the GHSA-gjj9-j8wf-5x29, RLMA-2025-05893 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 node-base58 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 node-base58 (version 1.0.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging node-base58 across your stack and pipelines.

Malicious package

node-base58npm

node-base58 is a confirmed malicious npm package (MAL-2025-49262) that executes malicious code on install (malicious version 1.0.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in node-base58 (npm)

MAL-2025-49262

Immediate action

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

npm uninstall node-base58

What this malware does

The package node-base58 was found to contain malicious code.

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

1.0.1

Indicators of compromise (SHA-256)

1d966f73ad19ab1fb24763cb1937d69690004b818fc7ca4b301b13c122da974b

e650ba35532afdff95942d9f08f3eae361d1b7481551253361b299bdb8354599

311fd3aad808982d8b727393d821147335d8dad899806d5582c2c8bf48fc0717

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for node-base58 (version 1.0.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging node-base58 across your stack and pipelines.
If you installed it — respond
Remove node-base58 from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If node-base58 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 node-base58 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. node-base58 on npm has been identified as a malicious package (version 1.0.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-gjj9-j8wf-5x29RLMA-2025-05893

References

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks node-base58-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