Which versions of eth-react-provider are malicious?

The following npm versions of eth-react-provider are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate eth-react-provider if I installed it?

eth-react-provider is a typosquat — you almost certainly intended a legitimately-named package. Remove eth-react-provider, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.

I already installed eth-react-provider — how do I know if it already compromised me?

If eth-react-provider 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 eth-react-provider part of a known attack campaign?

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

Malicious package

eth-react-providernpm

eth-react-provider is a confirmed malicious npm package (MAL-2026-14300) that typosquats a legitimate package to trick installs (malicious version 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in eth-react-provider (npm)

MAL-2026-14300

Immediate action

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

npm uninstall eth-react-provider

What this malware does

The package advertises itself as a React Ethereum provider exporting EthereumProvider/useProvider/useSigner/useNetwork hooks, but the shipped main entry lib/index.js contains web3.js Subscriptions code plus a large obfuscated payload wrapped in a Function("ObbvO95", "...") constructor that is invoked at module load. The payload uses randomized hex-named identifiers, a signed-integer decode table, and a doubly-unicode-escaped string body to hide its behavior from static inspection. Any consumer that require('eth-react-provider') executes this opaque code in the installer's process. The src/index.js in the tarball contains the clean web3.js source without this payload, indicating the built artifact was tampered. The README/code mismatch (documented React hook API vs. actual web3.js Subscriptions plus loader) is consistent with a trojanized lookalike package rather than a broken release.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

7b9bdf79a694cbf6d1a840541b4c47fdac8dc6ac32f4b6a3d4887d5f81233387

Detection & response playbook

Typosquat

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for eth-react-provider (version 1.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging eth-react-provider across your stack and pipelines.
If you installed it — respond
eth-react-provider is a typosquat — you almost certainly intended a legitimately-named package. Remove eth-react-provider, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.
Did it already run?
If eth-react-provider 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 eth-react-provider 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. eth-react-provider on npm has been identified as a malicious package (version 1.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-018420

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks eth-react-provider-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