Malicious Code Detected in @zalastax/nolb-node-cw Package
Summary
MAL-2025-12619: Malicious code in @zalastax/nolb-node-cw (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
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
Background
The @zalastax/nolb-node-cw package is an npm library designed for cloud workload management. It provides functionalities that assist developers in deploying and managing cloud resources efficiently. However, it has been identified to contain malicious code, posing a significant security risk to applications that utilize it.
Vulnerability Detail
The vulnerability in the @zalastax/nolb-node-cw package stems from the inclusion of malicious code that can compromise the security of applications using this package. This code may lead to unauthorized access, data breaches, or other malicious activities. 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-cwIf 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 workaround, consider using alternative packages that provide similar functionalities without the associated risks. Always review the security status of any package before integrating it into your project.
Conclusion
The @zalastax/nolb-node-cw package has been identified to contain malicious code, posing a serious threat to applications that utilize it. Users are urged to remove the package and seek alternatives until a secure version is released. Regular monitoring of dependencies is essential to maintain application security.
See every vulnerability recorded for @zalastax/nolb-node-cw →
FAQ
The malicious code can lead to unauthorized access and potential data breaches, compromising the security of applications.
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.
It is advisable to remove the package immediately and look for alternative solutions that do not pose security risks.
Currently, there is no patched version available. Users should remove the package until a secure version is released.
Regularly audit your dependencies using tools like Vulert and keep your packages updated to the latest secure versions.
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
