Which versions of @ensdomains/blacklist are malicious?

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

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

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

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

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

Malicious package

@ensdomains/blacklistnpm

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

MAL-2025-190722

Immediate action

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

npm uninstall @ensdomains/blacklist

What this malware does

The package @ensdomains/blacklist 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.0.1

Indicators of compromise (SHA-256)

07bcfb9c86c46e63aa1dc427bf998d8bb29b002edb2a3b85fb593c886af8bf01

885b443e4475d3f0306ce0899d0afd3b9190193bac49fa411c41328695e05a46

9a1817b9781032c47d48b86d10af22a4a6dcea47106a8d931c0ad0299d284543

74dabe3bb82f165d2966ff19d74b4196e5b03c4550bec0a861e1159146193514

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

Campaign

GHSA-hmjx-cmm9-gq7m

References

Credits

Amazon Inspector · finder

Detect & block this

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