Critical Malicious Code Vulnerability in debug-fmt Package
Summary
MAL-2026-566: Malicious code in debug-fmt (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-fmt package is a Node.js library used for formatting debug messages. It is commonly utilized in various applications to enhance logging capabilities. However, this package has been compromised, leading to significant security risks for any system that has it installed. The malicious code embedded within can potentially grant unauthorized access to sensitive information stored on the affected system.
Vulnerability Detail
The vulnerability stems from the presence of malicious code within the debug-fmt package, identified as GHSA-hvhh-9q7c-6g8m. This code can fully compromise any computer running the package, allowing attackers to access secrets and keys stored on the system. The implications of this vulnerability are severe, as it may lead to data breaches and unauthorized control over the affected machines. Users are advised to treat any system with this package installed as compromised.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall debug-fmtIf 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
Currently, there are no effective workarounds to mitigate the risks posed by the debug-fmt package. The only recommended action is to uninstall the package immediately.
Conclusion
The debug-fmt package has been compromised with malicious code, posing significant risks to any system using it. Immediate action is required to remove the package and secure any sensitive information. Regular monitoring for vulnerabilities using tools like Vulert can help prevent future incidents.
See every vulnerability recorded for debug-fmt →
FAQ
You should uninstall the debug-fmt package immediately and rotate any secrets or keys 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 sensitive data and potential control over your system by malicious actors.
Currently, there is no patched version available. The best course of action is to remove the package entirely.
Vulert uses package-lock.json to monitor and alert in real-time for open-source vulnerabilities in your software, providing an easy way to stay informed.
