Malicious Code Detected in @zalastax/nolb-nodejs_ Package
Summary
MAL-2025-12773: Malicious code in @zalastax/nolb-nodejs_ (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-nodejs_ package is a Node.js library designed for network load balancing. It provides developers with tools to manage and distribute incoming network traffic efficiently. However, it has been identified to contain malicious code, posing significant security risks to applications that utilize it.
Vulnerability Detail
The vulnerability stems from the inclusion of malicious code within the @zalastax/nolb-nodejs_ package. This code can potentially compromise the security of applications by allowing unauthorized access, data exfiltration, or other harmful activities. The malicious nature of this code was confirmed by security researchers, leading to its classification as a significant threat to users of the package.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall @zalastax/nolb-nodejs_If 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 measure, you can avoid using the @zalastax/nolb-nodejs_ package until a secure version is released. Additionally, you can implement strict input validation and monitoring to mitigate the risks associated with using compromised packages.
Conclusion
The discovery of malicious code in the @zalastax/nolb-nodejs_ package highlights the importance of vigilance in managing open-source dependencies. Users are advised to remove the package and monitor for updates or alternatives to ensure the security of their applications.
See every vulnerability recorded for @zalastax/nolb-nodejs_ →
FAQ
The malicious code can lead to unauthorized access and potential data breaches.
You can use Vulert to monitor your application for vulnerabilities by analyzing your package-lock.json file.
Yes, you can report vulnerabilities to the package maintainers or through security platforms that track open-source vulnerabilities.
Implement strict input validation and monitoring to reduce the risk of exploitation while you work on a permanent solution.
Yes, consider using other well-reviewed load balancing packages available in the npm ecosystem.
