Critical Malicious Code Vulnerability in @zalastax/nolb-node-4 Package
Summary
MAL-2025-12589: Malicious code in @zalastax/nolb-node-4 (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-4 package is an npm library designed for Node.js applications, providing various functionalities for developers. However, it has been identified to contain malicious code that poses significant security risks to applications utilizing this package. This vulnerability can lead to unauthorized access or data breaches, making it crucial for users to address it promptly.
Vulnerability Detail
The vulnerability in the @zalastax/nolb-node-4 package stems from the inclusion of malicious code that can compromise the security of applications. This code was introduced in version 0 and can lead to severe ramifications, including unauthorized data access and potential exploitation of the affected systems. The malicious nature of this code makes it imperative for users to take immediate action to mitigate risks.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall @zalastax/nolb-node-4If 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, you can remove the @zalastax/nolb-node-4 package from your project by executing: npm uninstall @zalastax/nolb-node-4. This will prevent any malicious code from executing while you await a secure update.
Conclusion
The @zalastax/nolb-node-4 package contains a critical vulnerability due to malicious code that can severely impact application security. Users are urged to update or remove the package to mitigate risks. Staying informed about vulnerabilities through tools like Vulert can help maintain the security of your applications.
See every vulnerability recorded for @zalastax/nolb-node-4 →
FAQ
The malicious code can compromise application security, potentially allowing unauthorized access to sensitive data.
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.
Currently, there is no patched version available. It is advisable to remove the package until a secure version is released.
If immediate removal is not possible, ensure that your application is secured and monitor for any suspicious activity until the package can be updated or removed.
Utilize tools like Vulert, which can monitor your package-lock.json file for vulnerabilities and alert you in real-time.
