Which versions of @zzzcrypto/etherjs are malicious?

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

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

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

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

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

Malicious package

@zzzcrypto/etherjsnpm

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

Malicious code in @zzzcrypto/etherjs (npm)

MAL-2026-13212

Immediate action

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

npm uninstall @zzzcrypto/etherjs

What this malware does

@zzzcrypto/etherjs is a typosquat of the popular 'ethers' package. On require(), index.js collects the full process.env object along with hostname, username, homedir, platform, cwd, and package identifiers, JSON-serializes and base64-encodes the payload, and sends it via HTTPS GET to a hardcoded Telegram Bot API endpoint (bot token 7231970337, chat_id 8969499041). A temporary flag file suppresses repeat sends. In CI and developer environments, process.env routinely contains credential-shaped values (AWS_*, GITHUB_TOKEN, NPM_TOKEN, cloud and vendor API keys), all of which are captured. The internal payload identifies the package as '@wethenorth12/etherjs' — a different scope than the published name — and the package.json author field impersonates 'ricmoo', the real ethers maintainer, indicating a shared attack template reused across multiple malicious scoped typosquats of ethers.

Malicious versions

1 flagged

6.15.4

Indicators of compromise (SHA-256)

b2aebef684ec4affb6c5d0504179ef4e4f409bf6680cdd6d70772ec8f9b3bf35

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

Campaign

IN-MAL-2026-015735

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

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