Malicious Code Detected in @zalastax/nolb-nodeb Package
Summary
MAL-2025-12708: Malicious code in @zalastax/nolb-nodeb (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-nodeb package is an npm library designed for specific functionalities within Node.js applications. It is utilized by developers for its ease of integration and performance. However, recent findings have revealed that this package contains malicious code, posing significant risks to applications that depend on it.
Vulnerability Detail
The vulnerability in the @zalastax/nolb-nodeb package stems from the inclusion of malicious code that can compromise the security of applications using this library. This code may lead to unauthorized access, data breaches, or other harmful actions within the affected systems. The malicious nature of this vulnerability was identified by Amazon Inspector, highlighting the importance of vigilance when using third-party packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall @zalastax/nolb-nodebIf 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-nodeb package from your project until a secure version is released. You can do this by executing the following command: npm uninstall @zalastax/nolb-nodeb.
Conclusion
The discovery of malicious code in the @zalastax/nolb-nodeb package underscores the importance of maintaining secure dependencies in software development. By staying informed and proactive, developers can mitigate risks associated with open-source libraries.
See every vulnerability recorded for @zalastax/nolb-nodeb →
FAQ
The malicious code can lead to unauthorized access and potential data breaches within applications using this package.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Check your application using the Vulert playground at Vulert Scanner.
If an immediate update is not possible, consider removing the package from your project as a temporary measure.
The vulnerability was identified by Amazon Inspector, a security assessment service.
Yes, tools like Vulert can automate the monitoring of your dependencies for vulnerabilities without requiring access to the code.
