Critical Malicious Code Vulnerability in @zalastax/nolb-node-o Package
Summary
MAL-2025-12633: Malicious code in @zalastax/nolb-node-o (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-o package is an npm library designed for Node.js applications, providing specific functionalities that enhance the development process. However, it has been identified to contain malicious code, posing significant security risks to applications that utilize it. This vulnerability can lead to unauthorized access, data breaches, and other malicious activities.
Vulnerability Detail
The vulnerability originates from the inclusion of malicious code within the @zalastax/nolb-node-o package. This code can execute harmful actions without the user's consent, potentially compromising the integrity and security of the application. The malicious nature of this code can lead to severe ramifications, including data theft, unauthorized access to sensitive information, and exploitation of the application for further attacks.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall @zalastax/nolb-node-oIf 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 avoid using the @zalastax/nolb-node-o package and look for alternative packages that provide similar functionality without the associated risks. Additionally, you can implement security measures such as input validation and output encoding to mitigate potential threats while transitioning to a safer package.
Conclusion
The @zalastax/nolb-node-o package has been identified to contain malicious code, posing serious security risks to applications that utilize it. It is crucial to take immediate action to remove the package and replace it with a secure alternative. Utilizing tools like Vulert can help monitor and alert for such vulnerabilities in real-time.
See every vulnerability recorded for @zalastax/nolb-node-o →
FAQ
The malicious code is designed to execute harmful actions without user consent, potentially compromising application security.
You can use Vulert, which monitors and alerts in real-time for open-source vulnerabilities. By checking your package-lock.json file, you can determine if your application is affected.
If immediate updates are not possible, consider implementing security measures and using alternative packages to mitigate risks.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.
Failure to address this vulnerability can lead to data breaches, unauthorized access, and exploitation of your application, resulting in significant security risks.
