Critical Malicious Code Vulnerability in tools-component-library Package
Summary
MAL-2025-5523: Malicious code in tools-component-library (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 tools-component-library is an npm package designed to facilitate the development of various tools and components in JavaScript applications. It provides a set of utilities that developers can leverage to enhance their projects. However, this package has been compromised, leading to a significant security vulnerability that could expose users to malicious activities.
Vulnerability Detail
The vulnerability originates from a malicious code embedded within the tools-component-library package. Any system with this package installed is considered fully compromised, as it may allow unauthorized access to sensitive information, including secrets and keys. The implications of this vulnerability are severe, as it can lead to data breaches and loss of control over the affected systems. Users are advised to treat any machine running this package as potentially compromised and take immediate action.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall tools-component-library
If 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, if immediate removal is not feasible, consider isolating the affected environment and restricting its network access to minimize potential damage until the package can be safely removed.
Conclusion
The tools-component-library package has been identified as containing malicious code, posing a significant risk to users. Immediate action is required to remove the package and secure any sensitive information. Utilizing tools like Vulert can help in monitoring and managing vulnerabilities effectively.
See every vulnerability recorded for tools-component-library →
FAQ
Immediately remove the package and rotate any secrets or keys stored on the affected machine.
You can use Vulert's playground at Vulert Scanner to check if your application is affected without requiring any signup.
Failing to address this vulnerability can lead to unauthorized access to sensitive data and potential control over your systems by malicious actors.
Currently, there is no patched version available, and the best course of action is to remove the package entirely.
Vulert monitors and alerts for open-source vulnerabilities in your software using just the package-lock.json file, allowing for real-time updates.