Malicious Code Detected in @zalastax/nolb-node-rc Package
Summary
MAL-2025-12642: Malicious code in @zalastax/nolb-node-rc (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-rc package is an npm library designed for Node.js applications, providing functionalities that may include load balancing and resource management. 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-node-rc package. This code can potentially compromise the security of applications using the 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-rcIf 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 replacing the functionality provided by @zalastax/nolb-node-rc with an alternative package that does not have known vulnerabilities. Review your application's dependencies and assess the impact of removing this package.
Conclusion
The discovery of malicious code in the @zalastax/nolb-node-rc package highlights the importance of regularly auditing dependencies in software projects. Immediate action is required to mitigate risks associated with this vulnerability, including removing the affected package and monitoring for updates.
See every vulnerability recorded for @zalastax/nolb-node-rc →
FAQ
The malicious code can perform unauthorized actions within the application, 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.
If immediate removal is not possible, consider implementing strict access controls and monitoring to mitigate potential risks until the package can be replaced.
Yes, you can report vulnerabilities to the maintainers of the package through their official repository on GitHub.
If a patched version is released, updating to that version is essential. Always review the release notes for any security fixes.
