Malicious Code Detected in @zalastax/nolb-nodejsp Package
Summary
MAL-2025-12776: Malicious code in @zalastax/nolb-nodejsp (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-nodejsp package is an npm library designed for Node.js applications, providing functionalities that facilitate the development of web applications. However, it has been identified to contain malicious code, posing significant risks to users and their applications. This vulnerability can lead to unauthorized access, data breaches, and other security issues.
Vulnerability Detail
The vulnerability originates from the inclusion of malicious code within the @zalastax/nolb-nodejsp package. This code can execute harmful operations without the user's consent, potentially compromising sensitive data and system integrity. Users of this package are at risk of exploitation, which can lead to severe consequences such as data loss, unauthorized access, and system failures.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall @zalastax/nolb-nodejspIf 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 measure, users can avoid using the @zalastax/nolb-nodejsp package until a secure version is released. Additionally, consider using alternative packages that provide similar functionalities without the associated risks.
Conclusion
The discovery of malicious code in the @zalastax/nolb-nodejsp package highlights the importance of vigilance in managing open-source dependencies. Users are urged to take immediate action by updating or replacing the affected package to safeguard their applications.
See every vulnerability recorded for @zalastax/nolb-nodejsp →
FAQ
The malicious code can perform unauthorized actions, potentially leading to data breaches and security vulnerabilities.
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.
Immediately update the package to the latest version or consider using an alternative package until a secure version is available.
Regularly update your dependencies, use tools like Vulert to monitor vulnerabilities, and review package code when possible.
Yes, you can report vulnerabilities to the package maintainers or through platforms like GitHub, where the package is hosted.
