Malicious Code Detected in @zalastax/nolb-node-2 Package
Summary
MAL-2025-12587: Malicious code in @zalastax/nolb-node-2 (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 @zalastax/nolb-node-2 package is an npm library designed for Node.js applications, providing functionalities that may include networking or load balancing features. However, it has been identified as containing malicious code, which poses a significant risk to users and their applications. This vulnerability can lead to unauthorized access or manipulation of data, making it crucial for developers to address it promptly.
Vulnerability Detail
The vulnerability in the @zalastax/nolb-node-2 package stems from the inclusion of malicious code that can compromise the security of applications utilizing this package. The malicious code can lead to data breaches, unauthorized access, or even complete takeover of the affected systems. This issue was introduced in version 0 and affects all subsequent versions, making it imperative for users to take immediate action to mitigate the risks associated with this vulnerability.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall @zalastax/nolb-node-2If 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 temporary workaround, users can isolate the affected package by using a different version of Node.js or by implementing strict access controls to limit the impact of the malicious code. However, the best practice remains to remove the package entirely until a secure alternative is found.
Conclusion
The discovery of malicious code in the @zalastax/nolb-node-2 package highlights the importance of vigilance in managing open-source dependencies. Users must take immediate action to remove the affected package and monitor for any updates or alternatives to ensure the security of their applications.
See every vulnerability recorded for @zalastax/nolb-node-2 →
FAQ
The malicious code can lead to unauthorized access and manipulation of data within applications that utilize this package.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check your application without any signup.
Currently, there is no patched version available for the @zalastax/nolb-node-2 package. Users are advised to remove it from their projects.
You should remove the @zalastax/nolb-node-2 package from your project and consider using a secure alternative.
Regularly monitor your dependencies using tools like Vulert, and keep your packages updated to the latest secure versions.
