Malicious Code Detected in @zalastax/nolb-node-g Package
Summary
MAL-2025-12625: Malicious code in @zalastax/nolb-node-g (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-g package is an npm library designed for Node.js applications, providing various functionalities that developers can leverage in their projects. However, this package has been flagged for containing malicious code, which poses significant risks to users and their applications.
Vulnerability Detail
The vulnerability stems from the presence of malicious code within the @zalastax/nolb-node-g package. This code can potentially compromise the security of applications that utilize this package, leading to unauthorized access, data breaches, or other malicious activities. The issue was introduced in version 0 and affects all subsequent versions.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall @zalastax/nolb-node-gIf 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 workaround, consider using alternative packages that provide similar functionalities without the associated risks. Always review the security status of any package before integrating it into your project.
Conclusion
The discovery of malicious code in the @zalastax/nolb-node-g package highlights the importance of vigilance when using open-source libraries. Users are advised to remove the affected package and consider alternatives to safeguard their applications.
See every vulnerability recorded for @zalastax/nolb-node-g →
FAQ
The malicious code can perform unauthorized actions within applications, potentially leading to data theft or system compromise.
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.
It is crucial to remove the package immediately and replace it with a safer alternative.
Yes, there are several alternative packages available on npm that provide similar functionalities without the associated risks. Research and select a reputable package.
Utilize tools like Vulert to monitor your dependencies for vulnerabilities and receive alerts in real-time.
