Which versions of @ensdomains/web3modal are malicious?

The following npm versions of @ensdomains/web3modal are flagged malicious: 1.10.2. Treat any of these as compromised.

How do I remediate @ensdomains/web3modal if I installed it?

@ensdomains/web3modal 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 @ensdomains/web3modal — how do I know if it already compromised me?

If @ensdomains/web3modal 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 @ensdomains/web3modal part of a known attack campaign?

Yes — @ensdomains/web3modal is associated with the GHSA-8g58-jm4g-p8h5 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 @ensdomains/web3modal 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 @ensdomains/web3modal (version 1.10.2). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @ensdomains/web3modal across your stack and pipelines.

Malicious package

@ensdomains/web3modalnpm

Malicious code in @ensdomains/web3modal (npm) Remove it immediately and rotate any exposed credentials.

MAL-2025-190815

Immediate action

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

npm uninstall @ensdomains/web3modal

What this malware does

The package @ensdomains/web3modal was found to contain malicious code.

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.

This package was compromised by the Sha1-Hulud: The Second Coming NPM worm. The malicious payload steals tokens and credentials and publishes them to GitHub. The worm will propogate itself to NPM packages the user owns and establish persistence is a GitHub action. The package may also destroy the user's home directory.

Malicious versions

1 flagged

1.10.2

Indicators of compromise (SHA-256)

952767cc9d80812078ded92e2295b446cc32cd807caf59b400bfe35b53cf2229

0de2afae3cc53842a9517b3463d4a07b3945667241988137bdc9598a49b189ab

6bbc9892348b98d2f808b27e546a34fd97bd3cd537f17c4c85e07f20770e1fb9

fdb5e16af18ab003235e2a259d26daaf95ac29931dc1e0fc8ee815adc25779db

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 @ensdomains/web3modal (version 1.10.2). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @ensdomains/web3modal across your stack and pipelines.
If you installed it — respond
@ensdomains/web3modal 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 @ensdomains/web3modal 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 @ensdomains/web3modal 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. @ensdomains/web3modal on npm has been identified as a malicious package (version 1.10.2 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-8g58-jm4g-p8h5

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks @ensdomains/web3modal-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