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 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.

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?

Search your lockfiles and build artifacts for @zzzgenesis00/etherjs (version 6.15.0).

Part of a larger attack: @zzzgenesis00 published 22 malicious packages. See the full campaign →

Malicious package

@zzzgenesis00/etherjsnpm

Advisory published Aug 4, 2026Updated Aug 4, 2026

@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
Search your lockfiles and build artifacts for @zzzgenesis00/etherjs (version 6.15.0).
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 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/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