Which versions of web3-utils-crypto are malicious?

The following npm versions of web3-utils-crypto are flagged malicious: 1.10.4. Treat any of these as compromised.

How do I remediate web3-utils-crypto if I installed it?

web3-utils-crypto 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.

I already installed web3-utils-crypto — how do I know if it already compromised me?

If web3-utils-crypto 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 web3-utils-crypto part of a known attack campaign?

Yes — web3-utils-crypto is associated with the IN-MAL-2026-015784 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 web3-utils-crypto 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 web3-utils-crypto (version 1.10.4). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging web3-utils-crypto across your stack and pipelines.

Malicious package

web3-utils-cryptonpm

web3-utils-crypto is a confirmed malicious npm package (MAL-2026-13354) that steals credentials and exfiltrates sensitive data (malicious version 1.10.4). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in web3-utils-crypto (npm)

MAL-2026-13354

Immediate action

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

npm uninstall web3-utils-crypto

What this malware does

web3-utils-crypto impersonates the web3-utils library (package description: 'Drop-in replacement for web3-utils') and ships stub wallet APIs including generateMnemonic and createWallet that return non-functional random values. On require(), index.js serializes the full process.env plus os.hostname, username, homedir, platform, cwd, package name/version and timestamp, base64-encodes the payload, and sends it via HTTPS GET to https://api.telegram.org/bot<token>/sendMessage with chat_id 8969499041 (bot id 7231970337). A tmp flag file suppresses repeat sends. process.env on developer and CI machines routinely contains AWS_*, GITHUB_TOKEN, NPM_TOKEN, DB_PASSWORD and similar credentials, so any consumer that installs and loads this package leaks its full environment to the attacker-controlled Telegram chat.

Malicious versions

1 flagged

1.10.4

Indicators of compromise (SHA-256)

d1f0dfc7ad97140ef740758424cd859d9c25ee55a6d6346859cebaf1e64cdce9

Detection & response playbook

Credential / info stealer

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

Campaign

IN-MAL-2026-015784

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

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

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database