Critical Malicious Code Vulnerability in @webhighlights/shared-components Package
Summary
MAL-2025-4159: Malicious code in @webhighlights/shared-components (npm). Affects @webhighlights/shared-components versions 99.9.0. 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 @webhighlights/shared-components package is a widely used library in the npm ecosystem, designed to provide reusable UI components for web applications. It is known for its modular architecture and ease of integration, making it a popular choice among developers. However, recent findings have revealed a significant vulnerability that exposes users to potential malicious code execution.
Vulnerability Detail
The vulnerability identified as MAL-2025-4159 involves the presence of malicious code within version 99.9.0 of the @webhighlights/shared-components package. This malicious code can lead to unauthorized access, data breaches, or compromise of the application utilizing this package. The origin of this issue is linked to the package's distribution through npm, where it was found to contain harmful scripts that could execute without user consent.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall @webhighlights/shared-componentsIf 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
If immediate updating is not feasible, consider removing the package temporarily or replacing it with an alternative library that provides similar functionality without the associated risks. Additionally, you can implement security measures such as input validation and monitoring to mitigate potential threats.
Conclusion
The @webhighlights/shared-components package has been identified with a critical vulnerability due to malicious code in version 99.9.0. It is crucial for developers using this package to take immediate action by updating to a secure version or implementing workarounds to safeguard their applications. Regular monitoring of dependencies using tools like Vulert can help maintain security in your projects.
See every vulnerability recorded for @webhighlights/shared-components →
FAQ
The vulnerability involves malicious code embedded in the package, which can lead to unauthorized actions within applications that use it.
You can use Vulert, which monitors open-source vulnerabilities in real-time. By analyzing your package-lock.json file, Vulert can alert you to any vulnerabilities, including this one.
Consider removing the package or using an alternative library until you can update to a secure version.
Detailed information can be found in the vulnerability report on GitHub or through the npm advisory database.
Yes, using tools like Vulert, you can automate the monitoring of your dependencies for vulnerabilities without needing to access the code directly.
