Malicious Code Detected in browser-html-to-rtf Package
Summary
MAL-2025-16197: Malicious code in browser-html-to-rtf (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 browser-html-to-rtf package is an npm library designed to convert HTML content into RTF (Rich Text Format) documents. It is commonly used in web applications that require document generation from HTML. However, this package has been identified to contain malicious code, posing significant security risks to applications that utilize it.
Vulnerability Detail
The vulnerability in the browser-html-to-rtf package stems from the inclusion of malicious code that can compromise the integrity and security of applications using this library. This code may lead to unauthorized access, data breaches, or other harmful effects on the system. The malicious nature of the code was discovered by security researchers, highlighting the importance of scrutinizing third-party packages for potential threats.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall browser-html-to-rtfIf 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, consider removing the browser-html-to-rtf package from your project until a secure version is released. You can uninstall it using the command: npm uninstall browser-html-to-rtf. Alternatively, explore other libraries that provide similar functionality without the associated risks.
Conclusion
The discovery of malicious code in the browser-html-to-rtf package underscores the importance of vigilance when using third-party libraries. Developers should take immediate action to mitigate risks by updating or removing the affected package and utilizing tools like Vulert for ongoing vulnerability monitoring.
See every vulnerability recorded for browser-html-to-rtf →
FAQ
The malicious code can potentially compromise application security, leading to unauthorized access or data breaches.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check if your application is affected without requiring any signup.
Currently, there is no specific patch version mentioned, but it is advisable to keep an eye on the package repository for any updates.
Consider removing the package from your project or using alternative libraries until a secure version is available.
Regularly audit your dependencies, use tools like Vulert for monitoring, and stay updated on security advisories related to the packages you use.
