Malicious Code Detected in @zalastax/nolb-node-c- Package
Summary
MAL-2025-12597: Malicious code in @zalastax/nolb-node-c- (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-c- package is an npm library designed for specific functionalities within Node.js applications. It is utilized by developers for its ease of integration and various features. However, recent findings have revealed that this package contains malicious code, posing significant risks to applications that depend on it.
Vulnerability Detail
The vulnerability stems from the presence of malicious code within the @zalastax/nolb-node-c- package. This code can lead to unauthorized access, data breaches, and potential exploitation of the systems using this package. The malicious nature of the code was identified by security researchers, raising alarms about the integrity and safety of applications utilizing this library.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall @zalastax/nolb-node-c-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 workaround, consider removing the @zalastax/nolb-node-c- package from your project until a secure version is released. You can do this by executing: npm uninstall @zalastax/nolb-node-c-.
Conclusion
The discovery of malicious code in the @zalastax/nolb-node-c- package highlights the importance of vigilance in managing open-source dependencies. Developers should take immediate action to mitigate risks by updating or removing the affected package and utilizing tools like Vulert for ongoing monitoring.
See every vulnerability recorded for @zalastax/nolb-node-c- →
FAQ
The malicious code can potentially allow unauthorized access to systems and data breaches.
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 specific patch version mentioned. It is advisable to monitor the package repository for updates.
Consider removing the package from your project as a temporary measure until a secure version is available.
Regularly monitor your dependencies for vulnerabilities using tools like Vulert, and keep your packages updated.
