thirdwebbnpm
Advisory published Updated
thirdwebb is a confirmed malicious npm package (MAL-2026-6694) 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 thirdwebb (npm)
What this malware does
Malicious npm package published as part of a coordinated DeFi-themed infostealer campaign. thirdwebb 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.
Package name 'thirdwebb' differs from the established 'thirdweb' SDK by a single trailing character, a classic typosquat shape against a popular Web3 SDK. No installer-harm behavior was observed in the package's code (no exfiltration, no install-time fetch-and-execute, no silent relay, no credential distribution). Name-similarity alone is a subjective signal that benefits from human assessment of intent before a public block is issued.
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
Indicators of compromise (SHA-256)
Detection & response playbook
Credential / info stealerFind it
Search your lockfiles and build artifacts for thirdwebb (version 0.0.8).
If you installed it — respond
thirdwebb 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 thirdwebb 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
Campaign
References
Credits
- Amazon Inspector · finder
- SafeDep · finder
Detect & block this
O3 blocks thirdwebb-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.