Malicious Code Detected in @zalastax/nolb-node-d Package
Summary
MAL-2025-12622: Malicious code in @zalastax/nolb-node-d (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-d package is an npm library designed for specific Node.js functionalities. It is utilized by developers for various applications, but it has been found to contain malicious code that poses a significant risk to users. This vulnerability can compromise the security of applications relying on this package, making it crucial for developers to be aware of its implications.
Vulnerability Detail
The vulnerability in the @zalastax/nolb-node-d package stems from the inclusion of malicious code. This code can lead to unauthorized access, data breaches, or other harmful actions within applications that utilize this package. The issue was introduced in version 0 and affects all subsequent versions, making 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-node-dIf 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-node-d package from your project until a secure version is released. You can do this by running: npm uninstall @zalastax/nolb-node-d. This will prevent any potential exploitation of the malicious code while you await a fix.
Conclusion
The discovery of malicious code in the @zalastax/nolb-node-d package highlights the importance of vigilance in managing open-source dependencies. Developers should take immediate action to mitigate risks by updating or removing the affected package and utilizing tools like Vulert to monitor for vulnerabilities.
See every vulnerability recorded for @zalastax/nolb-node-d →
FAQ
The malicious code can lead to unauthorized access and potential data breaches in applications that use 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.
As of now, there is no patched version available. Users should monitor the package repository for updates.
If immediate removal is not possible, ensure to implement strict security measures and monitor your application closely for any unusual activity.
Regularly check your dependencies for updates and consider using tools like Vulert to receive real-time alerts on vulnerabilities.
