Malicious Code Detected in logback-classic Package - Critical Security Risk
Summary
MAL-2025-6102: Malicious code in logback-classic (npm). Affects logback-classic versions >= 1.2.13. 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 logback-classic package is a widely used logging framework for Java applications, providing a robust and flexible logging system. It is an essential component for developers looking to implement logging in their applications efficiently. However, recent findings have revealed that certain versions of this package contain embedded malicious code, posing significant security risks to any application utilizing it.
Vulnerability Detail
The vulnerability stems from the logback-classic package communicating with a domain associated with malicious activity. This indicates that the package may have been compromised, leading to potential unauthorized access and control over systems that have it installed. The malicious code embedded within the package can lead to severe ramifications, including data breaches, loss of sensitive information, and complete system compromise. Users are advised to treat any system running this package as fully compromised.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall logback-classicIf 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, users should consider removing the logback-classic package from their applications until a secure version is confirmed. This can be done using the command: npm uninstall logback-classic. However, it is essential to note that removing the package may not eliminate all malicious software that could have been installed as a result of using the compromised package.
Conclusion
The discovery of malicious code within the logback-classic package poses a significant threat to applications using it. Immediate action is required to update or remove the package to safeguard systems from potential compromise. Utilizing tools like Vulert can further enhance security by providing real-time monitoring for vulnerabilities.
See every vulnerability recorded for logback-classic →
FAQ
logback-classic is a logging framework for Java applications, providing a flexible and efficient logging system.
The malicious code was likely introduced through a compromised version of the package, which communicates with a domain linked to malicious activities.
If you have the logback-classic package installed, you should immediately update to the latest version or uninstall the package to mitigate security risks.
Yes, Vulert can monitor and alert you in real-time for open-source vulnerabilities using just your package-lock.json file, ensuring your application remains secure.
You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.
