Which versions of @ensdomains/mock are malicious?

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

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

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

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

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

Malicious package

@ensdomains/mocknpm

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

MAL-2025-190806

Immediate action

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

npm uninstall @ensdomains/mock

What this malware does

The package @ensdomains/mock 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

2.1.52

Indicators of compromise (SHA-256)

e5e3d7ebf0c01ec0fcf11c5473aa2d0ae19924590bc4f27ac7e988945272d550

aa69028234e7d9845b0190a845d7ed004315332e53db9625716d3e8c34f9d555

b04a9d3216dd3e06e72c9fca74b323edc96b14932a3f49900d82aedd2c3cb4ce

74524ad1e7bf50e30c5a8b84f91e40203c384f4deb584c53ed77008b2de0213b

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

Campaign

GHSA-w28r-89v6-j9w8

References

Credits

Amazon Inspector · finder

Detect & block this

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