Malicious Code Detected in @zalastax/nolb-node-cp Package
Summary
MAL-2025-12613: Malicious code in @zalastax/nolb-node-cp (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-cp package is an npm library designed for Node.js applications, providing functionalities related to node-based operations. However, it has been identified as containing malicious code, posing a significant risk to users who integrate it into their projects. This vulnerability can compromise the integrity and security of applications relying on this package.
Vulnerability Detail
The vulnerability stems from the presence of malicious code within the @zalastax/nolb-node-cp package. This code can lead to unauthorized access, data breaches, or other harmful actions that can affect the overall security of applications using this package. The issue was introduced in version 0 and affects all subsequent versions, making it critical for users to address this vulnerability promptly.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall @zalastax/nolb-node-cpIf 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, users can avoid using the @zalastax/nolb-node-cp package until a safe 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-node-cp package highlights the importance of vigilance when using open-source libraries. Users are urged to remove this package from their projects and monitor for updates. Utilizing tools like Vulert can help in identifying vulnerabilities in real-time, ensuring the security of your applications.
See every vulnerability recorded for @zalastax/nolb-node-cp →
FAQ
The malicious code can potentially allow unauthorized access to sensitive data or enable harmful actions within the application.
You can use Vulert, which monitors open-source vulnerabilities in real-time. By checking your package-lock.json file, Vulert can alert you to any vulnerabilities, including this one.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.
Immediately remove the @zalastax/nolb-node-cp package from your project and monitor for any updates or patches that may address the vulnerability.
Yes, consider researching and using other npm packages that provide similar functionalities without the security risks associated with @zalastax/nolb-node-cp.
