Malicious Code Detected in @zalastax/nolb-ext3 Package
Summary
MAL-2025-11394: Malicious code in @zalastax/nolb-ext3 (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-ext3 package is an npm library designed for extending functionalities in Node.js applications. It is utilized for various purposes, including enhancing load balancing capabilities. However, this package has been found to contain malicious code, posing significant risks to applications that depend on it.
Vulnerability Detail
The vulnerability in the @zalastax/nolb-ext3 package originates from the inclusion of malicious code that can compromise the security of applications using this library. This code could lead to unauthorized access, data breaches, or other harmful actions within the affected systems. The malicious nature of this code makes it imperative for developers to address this vulnerability promptly.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall @zalastax/nolb-ext3If 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 an immediate update is not possible, consider removing the @zalastax/nolb-ext3 package from your project until a secure version is released. You can do this by executing: npm uninstall @zalastax/nolb-ext3.
Conclusion
The discovery of malicious code in the @zalastax/nolb-ext3 package highlights the importance of vigilance in managing dependencies. Developers are urged to take immediate action to mitigate risks by updating or removing the affected package.
See every vulnerability recorded for @zalastax/nolb-ext3 →
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.
As of now, a patched version has not been specified. Keep an eye on the package repository for updates.
Consider removing the package from your project until a secure version is released.
Vulert uses your package-lock.json to alert you in real-time about open-source vulnerabilities without requiring code access.
