Which versions of @ensdomains/renewal-widget are malicious?

The following npm versions of @ensdomains/renewal-widget are flagged malicious: 0.1.10. Treat any of these as compromised.

How do I remediate @ensdomains/renewal-widget if I installed it?

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

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

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

Malicious package

@ensdomains/renewal-widgetnpm

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

MAL-2025-190735

Immediate action

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

npm uninstall @ensdomains/renewal-widget

What this malware does

The package @ensdomains/renewal-widget 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.1.10

Indicators of compromise (SHA-256)

829d1d59ae69f9302b70416ea10d9af93f698aa766f13bc38c7797b23acdf3dc

727920a0b3da80ce1061cf9557e1d3ef72a90618523b692406438b7150061dad

3edc3409701ab0fbea8680ab9b5be1776b61536d131d8d6e957405b5a8454832

f51b24c6be68fcc7d3a6d5ef82c31772727851241fcc9d9830540fdb9d5d8efc

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

Campaign

GHSA-mq34-p89p-8c9h

References

Credits

Amazon Inspector · finder

Detect & block this

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