Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Malicious package

base58-clinpm

base58-cli is a confirmed malicious npm package (MAL-2026-6918) that executes malicious code on install (malicious versions 1.0.0, 1.0.1, 1.0.2…). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in base58-cli (npm)

MAL-2026-6918
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall base58-cli

What this malware does

The package was found to contain malicious code or consuming dependency that contains 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

6 flagged
1.0.01.0.11.0.21.0.31.0.41.0.5

Indicators of compromise (SHA-256)

e5150699ab8b1562f8a66c2e76e827699859c9701620b41ae48befe0e9c81638
60a7d188e2cd79918987f2008e93bb80ea9979d791b357f8f7cfd892321ded6c
ae346bb9962fbf5faf57e8b8c0d2f490c99738178e9a49662f8e60cb175f7462
dbc332dd17b89cb7f3acf3a0c57d0a82a437e6204d3ec72958ba2d9fe263bf50
215488016e651a3f4437c891d00ac422971590d26ed7534146bb91bcc701b497
96268157391eee000957a3569a6639907b83d3ae89fb70c81e20564cb290c0bd
c5f73bd5b470e8376e83a2f97ecf7dab7bc60369cc68d96a91c604cabd8fb446

Detection & response playbook

Malicious package
  1. Find it

    Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for base58-cli (6 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging base58-cli across your stack and pipelines.

  2. If you installed it — respond

    Remove base58-cli 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.

  3. Did it already run?

    If base58-cli 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.

  4. How O3 protects you

    O3 blocks base58-cli 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. base58-cli on npm has been identified as a malicious package (versions 1.0.0, 1.0.1, 1.0.2, 1.0.3, 1.0.4, 1.0.5 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-fg2f-v569-6wqvIN-MAL-2026-008493IN-MAL-2026-008496IN-MAL-2026-008568IN-MAL-2026-008884IN-MAL-2026-008886IN-MAL-2026-008885

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks base58-cli-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.

Explore

base58-cli (npm) malicious package — MAL-2026-6918 | O3 Security