Critical Malicious Code Vulnerability in debug-glitz Package
Summary
MAL-2026-567: Malicious code in debug-glitz (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 debug-glitz package is a Node.js library used for enhancing debugging capabilities in applications. It provides developers with tools to better visualize and manage debugging processes. However, this package has been identified as containing malicious code, posing significant security risks to any system where it is installed.
Vulnerability Detail
The vulnerability originates from the inclusion of malicious code within the debug-glitz package. This code can compromise any computer that has the package installed, allowing unauthorized access to sensitive information such as secrets and keys. The presence of this malicious code means that systems are at risk of being fully compromised, and simply removing the package may not eliminate all traces of the malicious software.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall debug-glitzIf 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
There are no effective workarounds for this vulnerability other than removing the package and securing your system. Ensure that you monitor your system for any unusual activity following the removal.
Conclusion
The debug-glitz package has been identified as containing malicious code that can compromise systems. Immediate action is required to remove the package and secure any sensitive information. Utilizing tools like Vulert can help in monitoring for such vulnerabilities in the future.
See every vulnerability recorded for debug-glitz →
FAQ
Immediately remove the debug-glitz package and rotate any sensitive information stored on your system.
You can use Vulert's playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.
Failing to address this vulnerability can lead to unauthorized access to your system, data breaches, and potential loss of sensitive information.
Regularly monitor your dependencies for vulnerabilities using tools like Vulert, which can alert you in real-time for open-source vulnerabilities.
If immediate removal is not possible, ensure that you limit access to the affected system and monitor for any suspicious activity until you can safely remove the package.
