Which versions of @ensdomains/dnsprovejs are malicious?

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

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

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

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

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

Malicious package

@ensdomains/dnsprovejsnpm

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

MAL-2025-190727

Immediate action

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

npm uninstall @ensdomains/dnsprovejs

What this malware does

The package @ensdomains/dnsprovejs 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.5.3

Indicators of compromise (SHA-256)

7a9e0d84a3086a73ca491735fad4fc6fc01ff9453130fece8b7fffa52cde1717

cba062a1b19731497546d926af22ae0964962df93fc3bd059d0e66df0fd41521

40a5c74c10e0f0c8991a3613115b44784682ed0ce014d024b0d48d68112a15b5

411b7d0190dfa47626b76b3a62b0d21f6a9775bca04b4317359e3b5db85b41a6

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

Campaign

GHSA-rg64-7w6m-qmxj

References

Credits

Amazon Inspector · finder

Detect & block this

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