Which versions of npmjs_web3-util are malicious?

The following npm versions of npmjs_web3-util are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate npmjs_web3-util if I installed it?

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.

I already installed npmjs_web3-util — how do I know if it already compromised me?

If npmjs_web3-util 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.

Is npmjs_web3-util part of a known attack campaign?

Yes — npmjs_web3-util is associated with the IN-MAL-2026-002672, GHSA-qjvc-v9v6-xh96 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find npmjs_web3-util across my projects, lockfiles, and CI pipelines?

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

Malicious package

npmjs_web3-utilnpm

Malicious code in npmjs_web3-util (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-3768

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall npmjs_web3-util

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

1 flagged

1.0.0

Indicators of compromise (SHA-256)

263a0126b20b1d58bc0528a4b7bea19027b94383e00b5b9f03b712d96be89ca7

d3c0cd1a1716cccac34dbc67b699361e42946acfab12003fb1af5bb75699439b

Detection & response playbook

Typosquat

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for npmjs_web3-util (version 1.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging npmjs_web3-util across your stack and pipelines.
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 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.
How O3 protects you
O3 blocks npmjs_web3-util 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. npmjs_web3-util on npm has been identified as a malicious package (version 1.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-002672GHSA-qjvc-v9v6-xh96

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.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database