Which versions of @ensdomains/server-analytics are malicious?

The following npm versions of @ensdomains/server-analytics are flagged malicious: 0.0.2. Treat any of these as compromised.

How do I remediate @ensdomains/server-analytics if I installed it?

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

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

Yes — @ensdomains/server-analytics is associated with the GHSA-3fjg-x55j-v7fv 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/server-analytics 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/server-analytics (version 0.0.2). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @ensdomains/server-analytics across your stack and pipelines.

Malicious package

@ensdomains/server-analyticsnpm

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

MAL-2025-190811

Immediate action

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

npm uninstall @ensdomains/server-analytics

What this malware does

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

0.0.2

Indicators of compromise (SHA-256)

2ad1d2ea0ee4f7ec36dfc2a68e5c4f7c3b8047de032653cff51fab9dc4e729a7

94dd4c8b8f01e631a4c2d9a19e272458d58a22a5a20c89b97603a94e2b68c4a3

4cc8dfb691122572289ab94fe5d0673155ba6db752b8baf47a36e4d449f3501d

e97996202e7a5b0bb3a1fafe8f30b709de2ca1f63e29a69980eb8abf84aac244

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

Campaign

GHSA-3fjg-x55j-v7fv

References

Credits

Amazon Inspector · finder

Detect & block this

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