Which versions of wagmi_util are malicious?

The following npm versions of wagmi_util are flagged malicious: 3.6.19. Treat any of these as compromised.

How do I remediate wagmi_util if I installed it?

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

If wagmi_util was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Is wagmi_util part of a known attack campaign?

Yes — wagmi_util is associated with the IN-MAL-2026-007367 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_util across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for wagmi_util (version 3.6.19).

Malicious package

wagmi_utilnpm

Advisory published Jun 23, 2026Updated Jun 23, 2026

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

Malicious code in wagmi_util (npm)

MAL-2026-6347

Immediate action

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

npm uninstall wagmi_util

What this malware does

Package wagmi_util impersonates the popular wagmi package: it copies wagmi's tagline ("React Hooks for Ethereum"), re-exports wagmi's full React-hooks public API (WagmiProvider, useConnect, useWalletClient, useSignMessage, useSendTransaction, useWriteContract, etc.), and links to wagmi.sh in JSDoc — while being published by an unrelated author with no legitimate wagmi_util package existing under the wevm namespace. The package.json declares a runtime dependency on [email protected], but no source file in the package imports sync-external; every internal use of useSyncExternalStoreWithSelector imports the legitimate use-sync-external-store/shim/with-selector.js instead. Installing wagmi_util therefore silently pulls [email protected] into the installer's dependency tree even though the wrapper's own code never loads it. The wrapper itself is clean re-exports of wagmi; the attack surface is the unused-but-pinned transitive, which a developer choosing a wagmi-adjacent utility would not expect to receive.

Malicious versions

1 flagged

3.6.19

Indicators of compromise (SHA-256)

e44ca5f8da70044150618d34a591d8a6d72aa77a5e22eb30da3e86f4b74c76ef

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for wagmi_util (version 3.6.19).
If you installed it — respond
wagmi_util 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_util was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. wagmi_util on npm has been identified as a malicious package (version 3.6.19 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-007367

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks wagmi_util-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