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

base58-corenpm

base58-core is a confirmed malicious npm package (MAL-2026-6445) that steals credentials and exfiltrates sensitive data (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-core (npm)

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

What this malware does

The package advertises itself as a Base58 encoder/decoder but on require() schedules a delayed payload that performs multiple installer-side attacks. After a 72-hour activation delay, code in dist/index.cjs and dist/index.js enumerates installer-owned secret stores — MetaMask extension storage across Chrome/Chromium/Brave/Edge profiles, Telegram Desktop tdata sessions, ~/.ssh keys, ~/.npmrc _authToken values, browser profile inventories, and env/.env crypto secret variables — and POSTs the collected report to a hardcoded bare-IP endpoint at http://2.27.62.51:8080/api/health (with:8081 as backup). A setInterval clipboard monitor invokes pbpaste/xclip/PowerShell via child_process every 2.5 seconds, matches BTC/ETH/SOL address regexes plus WIF private keys, BIP39 seed phrases (12–24 words), and 64-hex private keys, rewrites detected wallet addresses to attacker-controlled destinations (bc1qjft978uykglsh0adcyx6xhkes56vqzs3fual3l, 0xd63eD44065eDb1e2ad2519B011c06412dA7B7c5B, A7ajd7W5WYdrnkeaiBRjVoK6uBEDvgnuZcpzQXqo18Ph), writes them back to the clipboard, and exfiltrates matched values and the original clipboard slice to the same endpoint. A persistence routine appends a node -e loader to ~/.bashrc, ~/.zshrc, and ~/.profile that re-invokes the payload on every shell start; on Windows it drops base58-runtime.js into the user Startup folder, keeping the clipboard hijacker and exfil active across reboots and beyond project uninstall. The 72-hour dormancy timer is designed to evade sandbox and CI dynamic analysis. The package name and keywords (bitcoin/solana/wallet/ipfs) impersonate legitimate Base58 libraries to target crypto developers.

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

12 flagged
1.0.01.0.11.0.21.0.31.0.41.0.51.0.61.0.71.0.81.0.101.0.111.0.12

Indicators of compromise (SHA-256)

6e2594f5ee1ee71b3fb6a42fd834dee3598ce0993bd5718769dad01c916326d1
c10874ae13f1937b6974bcaaec72996e54f85fc3de6bf5e53d732f6e1f37c8a3
a01cd093c49b1f8e97a1a4b1f3711ee39c83235f9165cd8650cf18ff7bb56f7f
1b1217d46a6b8bcdefc7ac0e928e40e5e74985b4ed430870e0ce1703f0caef69
0081cc9c4152afede923a3e8ee9eb2116b32c02b7f355edbd411f23b2e67273c
68c7a1f450b6c157edaef60638c547dfb284623a9a77e27a0abc9ebfaff87d83
11db28718aa0b66d4fd60e20b771e15b5d6105966450c67723397b74bc59bd32
547f3bde449b07eb12b34eefeb82df3c8994111951215f2870606b6a72d433b0
fd61d8ee71e80b258f57bd2c02e48e132cd021a8fb4dbcf456e6a4ab63af73d0
048a186e2e59bb0b7d9986c7099e527390e38690292bc49e237578a471c56680
417a523add23d6946f26c4947dcd8db13d011ce847d03773c2da03945a6b4510
df9bd7c3c83faab169afcb367f345db46d0eaeeeaa4e2ea010e0d8b01eb82973
e697e341b967e796e17cc132952e12802f5e4e6ce8be1453d0434bf6c308081f

Detection & response playbook

Credential / info stealer
  1. Find it

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

  2. If you installed it — respond

    base58-core 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.

  3. Did it already run?

    If base58-core 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-core 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-core 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, 1.0.6, 1.0.7, and 4 more flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-007492IN-MAL-2026-007493IN-MAL-2026-007635IN-MAL-2026-007660IN-MAL-2026-007709IN-MAL-2026-007708IN-MAL-2026-007840IN-MAL-2026-007841IN-MAL-2026-007837IN-MAL-2026-008017IN-MAL-2026-008016IN-MAL-2026-008015GHSA-3439-q8cv-mg5v

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks base58-core-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Explore

base58-core (npm) malicious package — MAL-2026-6445 | O3 Security