# MAL-2026-14300: Malicious code in eth-react-provider (npm)


- **Type:** Malicious package
- **Package:** `eth-react-provider` (npm)
- **Published:** 19 Aug 2026
- **Also known as:** GHSA-rr86-r66c-qc54

## What is MAL-2026-14300?

MAL-2026-14300 is a malicious package in eth-react-provider, published on 19 Aug 2026. 

### Official description

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.

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.

## What should I do about MAL-2026-14300?

Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.

## Fix prompt for AI coding agents

```text
MAL-2026-14300 is a malicious package: eth-react-provider (npm). Every version was published to cause harm.

Task:
1. Search this repository's dependency manifests and lockfiles for the package, including transitive dependencies.
2. If it is present, remove it, regenerate the lockfile with the project's package manager, and replace whatever it was used for.
3. List any CI runners, developer machines or containers that installed it, so their secrets can be rotated.
4. If the package is not used anywhere, say so and change nothing.

Reference: https://insights.sbomify.com/MAL-2026-14300/ (Markdown: https://insights.sbomify.com/MAL-2026-14300/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/MAL-2026-14300

---
From sbomify Insights: https://insights.sbomify.com/MAL-2026-14300/
Summaries are generated and may contain mistakes; the official description above is the record.