Which versions of ethers-provider2 are malicious?

The following npm versions of ethers-provider2 are flagged malicious: 1.18.0. Treat any of these as compromised.

How do I remediate ethers-provider2 if I installed it?

Remove ethers-provider2 from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

I already installed ethers-provider2 — how do I know if it already compromised me?

If ethers-provider2 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 ethers-provider2 part of a known attack campaign?

Yes — ethers-provider2 is associated with the GHSA-9p3m-hfp2-pjf4, RLMA-2025-01523, RLUA-2025-02241, RLUA-2025-06349 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 ethers-provider2 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 ethers-provider2 (version 1.18.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging ethers-provider2 across your stack and pipelines.

Malicious package

ethers-provider2npm

ethers-provider2 is a confirmed malicious npm package (MAL-2025-2731) that executes malicious code on install (malicious version 1.18.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in ethers-provider2 (npm)

MAL-2025-2731

Immediate action

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

npm uninstall ethers-provider2

What this malware does

Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

Malicious versions

1 flagged

1.18.0

Indicators of compromise (SHA-256)

64291b6905fba089a2dada5e0215c20954bf12f15f76d27c5c341d2b91baa81b

122fc9acf3e372f435f9f94125c1d07b7cb77c236cc803da55985956e1cc9e6c

d17b75e319df4631afbf0e4cbe74e42e7d61b9f65380a1eebd95b80cf178754f

569fa1afeecfd350176b679d3619c32e8f14136b204b85c6285570e273c641ad

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for ethers-provider2 (version 1.18.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging ethers-provider2 across your stack and pipelines.
If you installed it — respond
Remove ethers-provider2 from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If ethers-provider2 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 ethers-provider2 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. ethers-provider2 on npm has been identified as a malicious package (version 1.18.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-9p3m-hfp2-pjf4RLMA-2025-01523RLUA-2025-02241RLUA-2025-06349

References

Credits

ReversingLabs · finder

Detect & block this

O3 blocks ethers-provider2-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database