Which versions of @zzzgenesis00/etherjs are malicious?

The following npm versions of @zzzgenesis00/etherjs are flagged malicious: 6.15.0. Treat any of these as compromised.

How do I remediate @zzzgenesis00/etherjs if I installed it?

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

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

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

Malicious package

@zzzgenesis00/etherjsnpm

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

Malicious code in @zzzgenesis00/etherjs (npm)

MAL-2026-11530

Immediate action

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

npm uninstall @zzzgenesis00/etherjs

What this malware does

The package is published as @zzzgenesis00/etherjs with author 'ricmoo' and a description mimicking the legitimate ethers.js library. On npm install, postinstall.js executes and enumerates installer-side secrets: ~/.ssh (private key file names and sizes), ~/.npmrc, ~/.gitconfig, Chrome and Firefox profile data (cookies/logins), cryptocurrency wallet directories (.bitcoin,.ethereum,.metamask,.exodus,.electrum, and similar), and named crypto/CI environment variables. The collected profile is POSTed to the Telegram Bot API (api.telegram.org/bot<token>/sendMessage with a hardcoded bot token and chat id) and to a hardcoded C2 endpoint at 40f955f39128bd79-178-249-214-24.serveousercontent.com/collect. The package name and spoofed authorship target developers seeking the legitimate ethers library.

Malicious versions

1 flagged

6.15.0

Indicators of compromise (SHA-256)

bc49c7ec56350694f458d9468efb51a30a9ac20ff490ac44b0cedd8bbbe004a5

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/etherjs (version 6.15.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @zzzgenesis00/etherjs across your stack and pipelines.
If you installed it — respond
@zzzgenesis00/etherjs 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/etherjs 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/etherjs 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/etherjs on npm has been identified as a malicious package (version 6.15.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-011352

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

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