Which versions of @ensdomains/subdomain-registrar are malicious?

The following npm versions of @ensdomains/subdomain-registrar are flagged malicious: 0.2.4. Treat any of these as compromised.

How do I remediate @ensdomains/subdomain-registrar if I installed it?

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

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

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

Malicious package

@ensdomains/subdomain-registrarnpm

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

MAL-2025-190812

Immediate action

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

npm uninstall @ensdomains/subdomain-registrar

What this malware does

The package @ensdomains/subdomain-registrar 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.2.4

Indicators of compromise (SHA-256)

5a8bbc5751d5df4950e6276acee56cd7c6e77067ab50b19e5f65a5b8e1f0bc4a

401414959edb6c3fa49058cca521272f84ed2c1e5aef8d7cacadb50696789ba5

31a568985b248d05ca367f19d12ed1dabc6cafa55ff9b13d4d41fa172d395f6b

bccf3e2efb0bb45a910c0baf52766e3dbe7b3da9d7592d9b55016dd22e923656

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

Campaign

GHSA-8fxj-7qgm-q65w

References

Credits

Amazon Inspector · finder

Detect & block this

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