NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
Malicious package

thirdwbnpm

Advisory published Updated

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

Malicious code in thirdwb (npm)

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

What this malware does

Malicious npm package published as part of a coordinated DeFi-themed infostealer campaign. thirdwb is a typosquat of the legitimate thirdweb package. It uses a side-loader technique, pulling in log-taker as a transitive dependency; the infostealer runs automatically via that dependency's postinstall hook. The payload harvests cryptocurrency wallet vaults (MetaMask, Phantom, Solflare, OKX, Coinbase, TrustWallet, Backpack, TronLink), browser cookies and credentials, SSH keys, AWS credentials, .npmrc tokens, Docker config, shell history, and password manager databases, exfiltrating all data to the C2 domain log-taker.store.

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

1 flagged
0.0.8

Indicators of compromise (SHA-256)

46722968fbda27cc58821cf8eb055f9c299d3984f794bc6c8554183a11f71304
7004be2aa6329c3eddda9d9809f0f87e06a14d60ddf9ad3f25b06675c1df6a83

Detection & response playbook

Credential / info stealer
  1. Find it

    Search your lockfiles and build artifacts for thirdwb (version 0.0.8).

  2. If you installed it — respond

    thirdwb 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 thirdwb was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. thirdwb on npm has been identified as a malicious package (version 0.0.8 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-008897GHSA-ccmq-q5j8-hvxc

References

Credits

  • Amazon Inspector · finder
  • SafeDep · finder

Detect & block this

O3 blocks thirdwb-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

thirdwb (npm) malicious package — MAL-2026-6693 | O3 Security