Which versions of @wethenorth12/ethers-wallet are malicious?

The following npm versions of @wethenorth12/ethers-wallet are flagged malicious: 6.13.5. Treat any of these as compromised.

How do I remediate @wethenorth12/ethers-wallet if I installed it?

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

If @wethenorth12/ethers-wallet 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 @wethenorth12/ethers-wallet part of a known attack campaign?

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

Malicious package

@wethenorth12/ethers-walletnpm

@wethenorth12/ethers-wallet is a confirmed malicious npm package (MAL-2026-12094) that steals credentials and exfiltrates sensitive data (malicious version 6.13.5). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @wethenorth12/ethers-wallet (npm)

MAL-2026-12094

Immediate action

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

npm uninstall @wethenorth12/ethers-wallet

What this malware does

The package presents itself as a drop-in replacement for the ethers library (author metadata ethers-io, repository URL pointing at the legitimate ethers project) and re-exports require('ethers') to appear functional. On require, index.js builds a JSON payload containing the entire process.env dictionary plus hostname, username, home directory, platform, current working directory, and timestamp, base64-encodes it, and sends it via HTTPS GET to a hardcoded Telegram Bot API sendMessage endpoint (bot id 7231970337, chat_id 8969499041). A tempdir flag file suppresses re-sends. In CI and developer environments process.env routinely contains AWS keys, npm tokens, GitHub tokens, and other credentials, so this constitutes bulk credential theft against any environment that installs or transitively loads the package.

Malicious versions

1 flagged

6.13.5

Indicators of compromise (SHA-256)

6460d1d0c9cc7423bb90aaf0b165fe45b3949fb627b33d817d34c1ffea64d3d8

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

Campaign

IN-MAL-2026-013439

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks @wethenorth12/ethers-wallet-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