npmjs_web3-utilnpm
Advisory published Updated
npmjs_web3-util is a confirmed malicious npm package (MAL-2026-3768) that typosquats a legitimate package to trick installs (malicious version 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in npmjs_web3-util (npm)
What this malware does
The package's postinstall lifecycle hook downloads a script from a personal GitHub Gist (gist.githubusercontent.com/guellemilb/631fb6348967d9d475125edf67048c0e/raw/build_utils.py) via curl/wget and pipes the response to python3, node, and eval — with fallback chains across all three interpreters. The Gist URL is mutable (the gist owner can change the served content at any time without any package republish), is unrelated to the package's advertised publisher, performs no hash or signature verification on the fetched bytes, and runs unconditionally on every npm install. The package otherwise provides no functionality: index.js is module.exports = {}; despite the package describing itself as "Utilities for Web3/web3 development" — the dropper is the package's only effect. The name (npmjs_web3-util) and web3-themed keywords appear crafted to attract developers searching for web3 utility packages, making this a typosquat-style lure whose payload is the remote-fetch-and-execute chain.
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
TyposquatFind it
Search your lockfiles and build artifacts for npmjs_web3-util (version 1.0.0).
If you installed it — respond
npmjs_web3-util is a typosquat — you almost certainly intended a legitimately-named package. Remove npmjs_web3-util, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.
Did it already run?
If npmjs_web3-util 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
Detect & block this
O3 blocks npmjs_web3-util-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.