Critical Malicious Code Vulnerability in cookie-logger Package
Summary
MAL-2025-6359: Malicious code in cookie-logger (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 cookie-logger package is an npm library designed to log cookies in a web application environment. It is often used by developers to track user sessions and manage cookie data effectively. However, this package has been identified to contain embedded malicious code that compromises the security of any system it is installed on, making it a significant risk for developers and organizations relying on it.
Vulnerability Detail
The vulnerability stems from the presence of embedded malicious code within the cookie-logger package. This code can lead to complete system compromise, allowing unauthorized access to sensitive information such as secrets and keys stored on the affected machine. The malicious nature of this code means that any system running this package is at high risk, and simply removing the package may not eliminate all traces of the malicious software introduced.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall cookie-loggerIf 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, the best workaround is to avoid using the cookie-logger package altogether. If you need similar functionality, consider using alternative packages that do not have known vulnerabilities.
Conclusion
The cookie-logger package contains malicious code that poses a serious risk to any system using it. Immediate action is required to remove the package and secure any compromised information. Utilizing tools like Vulert can help monitor and prevent future vulnerabilities.
See every vulnerability recorded for cookie-logger →
FAQ
Immediately remove the cookie-logger package from your project and rotate any sensitive information that may have been compromised.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check your application without requiring any signup.
Regularly audit your dependencies and use tools like Vulert to monitor for vulnerabilities in your open-source packages.
Ignoring this vulnerability can lead to unauthorized access to your system, data breaches, and potential loss of sensitive information.
Yes, consider using other logging packages that do not have known vulnerabilities, such as express-session or cookie-parser.
