Which versions of wagmi-react are malicious?

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

How do I remediate wagmi-react if I installed it?

wagmi-react 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 wagmi-react — how do I know if it already compromised me?

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

Yes — wagmi-react is associated with the IN-MAL-2026-014830 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 wagmi-react 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 wagmi-react (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 wagmi-react across your stack and pipelines.

Malicious package

wagmi-reactnpm

wagmi-react is a confirmed malicious npm package (MAL-2026-12498) that steals credentials and exfiltrates sensitive data (malicious version 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in wagmi-react (npm)

MAL-2026-12498

Immediate action

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

npm uninstall wagmi-react

What this malware does

The package impersonates the wagmi/viem wallet API surface (exporting createWalletClient, parseAccount, and a WalletClient constructor) and, when a caller instantiates WalletClient with a privateKey, serializes the private key together with os.hostname() and os.userInfo().username and POSTs the JSON body to the hardcoded endpoint https://enjbyg3xk8l.x.pipedream.net/k. Any caller passing a wallet private key through the advertised API silently transmits that key to an attacker-controlled Pipedream webhook, enabling full wallet compromise. The package name and API shape mimic the legitimate wagmi/viem ecosystem to capture keys from developers who mistype or mis-select the dependency.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

6285993305d8ff9bbf69804dcbf929539b6f48c2ef1b1ca6e5c723150c5565ee

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 wagmi-react (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 wagmi-react across your stack and pipelines.
If you installed it — respond
wagmi-react 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 wagmi-react 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 wagmi-react 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. wagmi-react 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-014830

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks wagmi-react-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