NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
Part of a larger attack: @zzzgenesis00 published 22 malicious packages. See the full campaign →
Malicious package

@zzzgenesis00/web3-provider-enginenpm

Advisory published Updated

@zzzgenesis00/web3-provider-engine is a confirmed malicious npm package (MAL-2026-11994) that steals credentials and exfiltrates sensitive data (malicious version 16.0.5). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @zzzgenesis00/web3-provider-engine (npm)

MAL-2026-11994
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall @zzzgenesis00/web3-provider-engine

What this malware does

Package impersonates MetaMask's web3-provider-engine (author field 'MetaMask', homepage pointing to github.com/MetaMask/web3-provider-engine) while shipping a postinstall.js that runs automatically on npm install and harvests installer secrets. postinstall.js reads ~/.ssh contents, ~/.npmrc, ~/.gitconfig, Chrome/Firefox profile databases (Cookies, Login Data, key4.db), enumerates crypto wallet directories (.bitcoin,.ethereum,.metamask,.exodus, and others), invokes npm whoami and git config, and captures roughly 30 credential-shaped environment variables including NPM_TOKEN, GITHUB_TOKEN, AWS keys, PRIVATE_KEY, MNEMONIC, SEED_PHRASE, and multiple chain-specific *_PRIVATE_KEY values. The collected data is JSON-serialized and transmitted to two hardcoded non-first-party destinations: api.telegram.org/bot<token>/sendMessage via GET with a hardcoded bot token and chat_id, and https://40f955f39128bd79-178-249-214-24.serveousercontent.com/collect via POST. index.js provides a stub web3 API surface (createWallet, generateMnemonic returning random bytes) to appear functional and disguise the harvest.

Malicious versions

1 flagged
16.0.5

Indicators of compromise (SHA-256)

fae571005ccdcdc23e50fbee1eddc31d39355706b7945df3ccbb3096ecaf724b

Detection & response playbook

Credential / info stealer

  1. Find it

    Search your lockfiles and build artifacts for @zzzgenesis00/web3-provider-engine (version 16.0.5).

  2. If you installed it — respond

    @zzzgenesis00/web3-provider-engine 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.

  3. Did it already run?

    If @zzzgenesis00/web3-provider-engine 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

No. @zzzgenesis00/web3-provider-engine on npm has been identified as a malicious package (version 16.0.5 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-011353

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks @zzzgenesis00/web3-provider-engine-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
@zzzgenesis00/web3-provider-engine (npm) malicious package — MAL-2026-11994 | O3 Security