Malicious code in @lognex/services-routing (npm)
Summary
MAL-2023-8634: Malicious code in @lognex/services-routing (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 @lognex/services-routing package is an npm package used for routing services. It provides functionality for routing requests to different services based on specific criteria. This package is commonly used in Node.js applications to handle routing logic. However, the package has been found to contain malicious code, which poses a significant security risk to any system that has it installed.
Vulnerability Detail
The vulnerability in @lognex/services-routing is due to the presence of malicious code in the package. This code can compromise the security of the system and give control to an external entity. Any computer with this package installed or running should be considered fully compromised. It is crucial to rotate all secrets and keys stored on the affected computer immediately from a different computer. Although removing the package is recommended, there is no guarantee that it will remove all the malicious software resulting from its installation.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall @lognex/services-routingIf 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
Unfortunately, there is no known workaround for this vulnerability. It is crucial to follow the steps mentioned in the 'how_to_fix' section to mitigate the risk and ensure the security of the system.
Conclusion
The presence of malicious code in the @lognex/services-routing package poses a significant security risk to any system that has it installed. It is crucial to take immediate action to mitigate the risk, including rotating secrets and keys, removing the package, and conducting a thorough security audit. For further support and assistance in vulnerability remediation, please contact DevNack.com.
See every vulnerability recorded for @lognex/services-routing →
FAQ
The impact of this vulnerability is severe. Any system with the @lognex/services-routing package installed or running should be considered fully compromised. It can lead to unauthorized access, data breaches, and potential control of the system by an external entity.
You can use the Vulert Playground (https://vulert.com/scanner) to check if your system is affected by this vulnerability. It analyzes the package-lock.json file and provides real-time alerts for open-source vulnerabilities.
Removing the package is recommended, but it may not remove all the malicious software resulting from its installation. It is crucial to rotate all secrets and keys stored on the affected computer and conduct a thorough security audit to ensure the system's integrity.
Specific exploits or attacks leveraging this vulnerability have not been disclosed at this time. However, given the nature of the malicious code, it is essential to assume that the system has been compromised and take appropriate measures to secure it.
If you find the @lognex/services-routing package in your project's dependencies, it is crucial to follow the steps mentioned in the 'how_to_fix' section. Additionally, consider conducting a thorough security audit to identify any potential unauthorized access or compromised data.
