Malicious Code Detected in @zalastax/nolb-node-st Package
Summary
MAL-2025-12694: Malicious code in @zalastax/nolb-node-st (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-st package is an npm library designed for specific functionalities within Node.js applications. It is utilized by developers for its features that enhance application performance and management. However, this package has been found to contain malicious code, posing significant risks to users who integrate it into their projects.
Vulnerability Detail
The vulnerability originates from the inclusion of malicious code within the @zalastax/nolb-node-st package. This code can lead to unauthorized access, data breaches, or other harmful actions within applications that utilize this package. The malicious nature of the code makes it imperative for developers to address this issue promptly to safeguard their applications and user data.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall @zalastax/nolb-node-stIf 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-st package from your project until a secure version is released. You can do this by executing the command: npm uninstall @zalastax/nolb-node-st. This will help mitigate the risks associated with the malicious code until a fix is available.
Conclusion
The discovery of malicious code in the @zalastax/nolb-node-st package highlights the importance of vigilance in managing open-source dependencies. Developers should take immediate action to update or remove the affected package to protect their applications and users.
See every vulnerability recorded for @zalastax/nolb-node-st →
FAQ
The malicious code can potentially allow unauthorized access to sensitive data and compromise application security.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check your application without needing to sign up.
If an immediate update is not possible, consider removing the package from your project as a temporary measure to prevent exploitation.
Yes, using tools like Vulert can help you monitor your dependencies for any new vulnerabilities as they arise.
You can find more information on its GitHub repository or npm page, where updates and documentation are provided.
