Critical Malicious Code Vulnerability in dompurifier Package
Summary
MAL-2025-18627: Malicious code in dompurifier (npm). Affected versions are not published. 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 dompurifier package is a widely used library in the npm ecosystem designed to sanitize HTML and prevent XSS (Cross-Site Scripting) attacks. It is known for its ability to clean user-generated content, ensuring that only safe HTML is rendered in web applications. However, a recent discovery has revealed that this package contains malicious code, posing significant security risks to applications that rely on it.
Vulnerability Detail
The vulnerability in the dompurifier package stems from the presence of malicious code that was introduced in all versions starting from 0. This code can potentially compromise the security of applications by allowing unauthorized access or manipulation of data. The malicious nature of this code can lead to severe ramifications, including data breaches, unauthorized actions, and exploitation of user trust.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall dompurifierIf 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 temporary workaround, you can remove the dompurifier package from your project until a secure version is released. You can do this by running: npm uninstall dompurifier. Consider using alternative libraries that provide similar functionality without the associated risks.
Conclusion
The discovery of malicious code in the dompurifier package highlights the importance of maintaining vigilance regarding open-source dependencies. It is essential to update to secure versions promptly and consider using monitoring tools like Vulert to stay informed about potential vulnerabilities.
See every vulnerability recorded for dompurifier →
FAQ
The dompurifier package is used to sanitize HTML content to prevent XSS attacks in web applications.
You can check if your application is affected by using Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to test your application without any signup.
If you cannot update the package right away, consider removing it from your project and using alternative libraries until a secure version is available.
The malicious code can compromise your application's security, leading to data breaches and unauthorized actions that can harm your users and your reputation.
Yes, you can use tools like Vulert, which allows you to monitor your dependencies for vulnerabilities in real-time using just your package-lock.json file.
