Critical Malicious Code Vulnerability in @ensdomains/blacklist Package
Summary
MAL-2025-190722: Malicious code in @ensdomains/blacklist (npm). Affects @ensdomains/blacklist versions 1.0.1. No fix is published. How to fix ↓
Check if this vulnerability affects your application
Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.
No signup required · Results in about 60 seconds
Background
The @ensdomains/blacklist package is a tool used within the npm ecosystem to manage and maintain a blacklist of domains. It is primarily utilized in applications that require domain validation and security measures against malicious domains. However, this package has been compromised, leading to significant security risks for any application that integrates it.
Vulnerability Detail
The vulnerability stems from the presence of embedded malicious code within the @ensdomains/blacklist package. This code can fully compromise any computer that has the package installed, allowing unauthorized access to sensitive information such as secrets and keys. The malicious nature of the code poses a severe risk, as it may not be entirely removed even after uninstalling the package, leaving systems vulnerable to further exploitation.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall @ensdomains/blacklistIf it arrived as a transitive dependency, remove the package that pulled it in, then reinstall.
Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →
Workaround
As a workaround, ensure that any applications using the @ensdomains/blacklist package are temporarily disabled until the package is removed and the system is secured. Regularly monitor your system for any unusual activity that may indicate ongoing malicious behavior.
Conclusion
The @ensdomains/blacklist package has been identified as containing malicious code, posing a significant security threat to any system utilizing it. Immediate action is required to remove the package and secure any sensitive information. Regular monitoring and security practices are essential to prevent future vulnerabilities.
See every vulnerability recorded for @ensdomains/blacklist →
FAQ
Immediately remove the package and rotate all sensitive information stored on the affected machine.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check your application without requiring any signup.
While removing the package is essential, there is no guarantee that all malicious software will be eliminated. It is advisable to perform a thorough security audit of the affected system.
Failure to address this vulnerability can lead to unauthorized access to sensitive data, potential data breaches, and further exploitation of the compromised system.
If a patched version is released, updating the package may resolve the issue. However, it is crucial to remove the compromised version first and ensure the system is secure.
