Critical Malicious Code Vulnerability in winston-compose Package
Summary
MAL-2025-6004: Malicious code in winston-compose (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 winston-compose package is a utility for composing multiple Winston loggers in Node.js applications. It allows developers to create complex logging configurations easily. However, this package has been compromised, embedding malicious code that poses significant security risks to any system using it.
Vulnerability Detail
The vulnerability originates from the inclusion of malicious code within the winston-compose package. This code can fully compromise any computer that has the package installed, allowing unauthorized access to sensitive information such as secrets and keys. The implications are severe, as attackers may gain complete control over the affected systems, making it critical for users to take immediate action.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall winston-composeIf 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, you can temporarily replace winston-compose with an alternative logging solution until the vulnerability is addressed. Consider using other logging libraries such as 'winston' or 'bunyan' that do not have known vulnerabilities.
Conclusion
The winston-compose 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. Users should consider alternative logging solutions and utilize tools like Vulert to monitor for vulnerabilities in their projects.
See every vulnerability recorded for winston-compose →
FAQ
Immediately remove the winston-compose package from your project and rotate any secrets or keys stored on the affected machine.
You can use Vulert to monitor and alert for open-source vulnerabilities in your software. Visit Vulert Scanner to check if your application is affected without needing to sign up.
The best mitigation is to remove the package entirely and replace it with a secure alternative logging solution.
Failure to address this vulnerability could lead to unauthorized access to sensitive data, complete system compromise, and potential data breaches.
Utilize tools like Vulert, which can monitor your package-lock.json file for vulnerabilities and provide real-time alerts.
