Critical Malicious Code Vulnerability in start-log-backend Package
Summary
MAL-2025-192758: Malicious code in start-log-backend (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
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 start-log-backend package is an npm module designed for backend logging functionalities in Node.js applications. It allows developers to manage and store logs efficiently. 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 start-log-backend package. This code can fully compromise any computer that has the package installed or running, allowing unauthorized access to sensitive information such as secrets and keys. The ramifications are severe, as attackers may gain complete control over the affected systems, leading to potential data breaches and exploitation.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall start-log-backendIf 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
There are no effective workarounds for this vulnerability other than removing the package and securing the system. Ensure that all sensitive data is rotated and that the system is monitored for any suspicious activity.
Conclusion
The start-log-backend package has been compromised with malicious code, posing serious security threats to any system using it. Immediate action is required to remove the package and secure sensitive information. Utilizing tools like Vulert can help monitor for such vulnerabilities in the future.
See every vulnerability recorded for start-log-backend →
FAQ
Immediately remove the package and rotate any secrets or keys stored on the affected system.
You can use the Vulert playground at Vulert Scanner to check if your application is affected without needing to sign up.
Failing to address this vulnerability can lead to unauthorized access to sensitive data, complete system compromise, and potential data breaches.
Currently, there is no patch available. The best course of action is to remove the package entirely.
Vulert monitors and alerts in real-time for open-source vulnerabilities using just the package-lock.json file, providing a seamless way to stay informed about potential 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.
