Malicious Code Vulnerability in session-keeper Package
Summary
MAL-2025-192861: Malicious code in session-keeper (npm). Affects session-keeper versions 2.4.5 – 2.5.5. 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
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
Background
The session-keeper package is a Node.js library designed to manage user sessions in web applications. It provides functionalities for creating, maintaining, and destroying user sessions securely. However, certain versions of this package have been found to contain malicious code, posing significant security risks to applications that rely on it.
Vulnerability Detail
The vulnerability identified in the session-keeper package is due to the presence of malicious code that can compromise user data and application integrity. This issue originated from specific versions of the package (2.4.5 and 2.5.5) that were tampered with, allowing attackers to execute arbitrary code within the application context. The ramifications include unauthorized access to sensitive information, potential data breaches, and exploitation of the application for further attacks.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall session-keeperIf 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
If immediate updating is not feasible, consider temporarily removing the session-keeper package from your project until a secure version is available. You can do this by executing: npm uninstall session-keeper.
Conclusion
The session-keeper package has a critical vulnerability due to malicious code present in specific versions. It is crucial for developers using this package to update to a secure version promptly to protect their applications and user data. Utilizing tools like Vulert can aid in monitoring for such vulnerabilities effectively.
See every vulnerability recorded for session-keeper →
FAQ
The affected versions of session-keeper are 2.4.5 and 2.5.5.
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.
Using the compromised session-keeper package can lead to unauthorized access to user data, potential data breaches, and exploitation of your application by attackers.
Yes, updating to the latest version of the session-keeper package will resolve the vulnerability.
If you cannot update the package immediately, consider uninstalling it or implementing additional security measures to mitigate risks.
References
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
