Which versions of @zzzgenesis00/web3-utils-crypto are malicious?

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

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

@zzzgenesis00/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 @zzzgenesis00/web3-utils-crypto — how do I know if it already compromised me?

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

Yes — @zzzgenesis00/web3-utils-crypto is associated with the IN-MAL-2026-014392 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 @zzzgenesis00/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 @zzzgenesis00/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 @zzzgenesis00/web3-utils-crypto across your stack and pipelines.

Malicious package

@zzzgenesis00/web3-utils-cryptonpm

@zzzgenesis00/web3-utils-crypto is a confirmed malicious npm package (MAL-2026-12125) 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 @zzzgenesis00/web3-utils-crypto (npm)

MAL-2026-12125

Immediate action

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

npm uninstall @zzzgenesis00/web3-utils-crypto

What this malware does

@zzzgenesis00/web3-utils-crypto ships a postinstall.js that runs automatically on npm install and harvests installer-side secrets and host data. The script reads ~/.ssh, ~/.npmrc, ~/.gitconfig, Chrome/Firefox profile artifacts, wallet directory presence, and enumerates a large list of credential-shaped environment variables (NPM_TOKEN, NODE_AUTH_TOKEN, GITHUB_TOKEN, AWS_*, PRIVATE_KEY, MNEMONIC, SEED_PHRASE, ETHEREUM_PRIVATE_KEY, and similar), together with hostname, username, homedir, platform/arch, cpu/mem, and cwd. It also invokes npm whoami. The collected JSON is transmitted to a hardcoded Telegram bot endpoint (api.telegram.org/bot<redacted>/sendMessage?chat_id=7231970337) and POSTed to a serveo.net SSH-tunnel subdomain at 40f955f39128bd79-178-249-214-24.serveousercontent.com/collect. Identifiers in the payload script are obfuscated (_syt, _bqi, _okl, _tk, _ch, _ex) and framed with cover-story comments (postinstall environment verification, Legitimate module passthrough); package.json impersonates the ChainSafe organization via a spoofed author field and homepage pointing at github.com/chainSafe/web3-utils-crypto.

Malicious versions

1 flagged

1.10.4

Indicators of compromise (SHA-256)

c5f75dc3a679eaa0579352bb4d345acb84247d70f4e4db06e5de04ff6d20f4e5

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 @zzzgenesis00/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 @zzzgenesis00/web3-utils-crypto across your stack and pipelines.
If you installed it — respond
@zzzgenesis00/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 @zzzgenesis00/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 @zzzgenesis00/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. @zzzgenesis00/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-014392

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks @zzzgenesis00/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