Malicious Code Detected in @zalastax/nolb-parser: A Critical Security Concern
Summary
MAL-2025-13000: Malicious code in @zalastax/nolb-parser (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 package @zalastax/nolb-parser is an npm library designed for parsing Network Load Balancer (NLB) configurations. It is utilized in various applications to facilitate the management and analysis of load balancer settings. However, the package has been found to contain malicious code, posing significant security risks to users who integrate it into their projects.
Vulnerability Detail
The vulnerability in the @zalastax/nolb-parser package originates from the inclusion of malicious code that can compromise the security of applications using this library. This code may allow unauthorized access, data exfiltration, or other harmful actions within the affected systems. The malicious nature of this vulnerability makes it imperative for users to take immediate action to mitigate potential risks.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall @zalastax/nolb-parserIf 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-parser package from your project until a secure version is released. You can do this by executing the following command: npm uninstall @zalastax/nolb-parser.
Conclusion
The discovery of malicious code in the @zalastax/nolb-parser package highlights the importance of vigilance in managing open-source dependencies. Users are strongly advised to update or remove the package to protect their applications from potential threats.
See every vulnerability recorded for @zalastax/nolb-parser →
FAQ
The malicious code can potentially allow unauthorized access to sensitive data and compromise the integrity of applications using the package.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check if your application is affected without requiring any signup.
If an immediate update is not possible, consider removing the package from your project as a temporary measure to mitigate risks.
While specific exploits have not been publicly disclosed, the presence of malicious code indicates a high risk of exploitation.
Regularly check the npm registry and security advisories for updates on the packages you use, and consider using tools like Vulert for real-time monitoring.
