Which versions of @ensdomains/cypress-metamask are malicious?

The following npm versions of @ensdomains/cypress-metamask are flagged malicious: 1.2.1. Treat any of these as compromised.

How do I remediate @ensdomains/cypress-metamask if I installed it?

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

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

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

Malicious package

@ensdomains/cypress-metamasknpm

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

MAL-2025-190803

Immediate action

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

npm uninstall @ensdomains/cypress-metamask

What this malware does

The package @ensdomains/cypress-metamask 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.

The OpenSSF Package Analysis project identified '@ensdomains/cypress-metamask' @ 1.2.1 (npm) as malicious.

It is considered malicious because:

The package executes one or more commands associated with malicious behavior.

Malicious versions

1 flagged

1.2.1

Indicators of compromise (SHA-256)

cab4b86ed1d6cd6c17668107ae3abc0bbe5bbc6fe156582d0809e77b0512c907

19427e64315a085f7001dff6a896730aa4cce33cf679f6a2da0a8bc61e96fb58

438db41a246affe115dcf7d8c5d2b2552f033ae736821d2c0c4c3b42f2da502e

a854d02edbe1ae8649c74d6af171b18b2fd75aaced12525a4208046d9b6f6bde

94ba569d22b14d43fa3d49e25d5bd0c46cb4b77b44d1115b0b440af39ff8e38f

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

Campaign

GHSA-xc86-vfw2-q5gj

References

Credits

Amazon Inspector · finder
OpenSSF: Package Analysis · finder

Detect & block this

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