Critical Malicious Code Vulnerability in @zalastax/nolb-node-w Package
Summary
MAL-2025-12703: Malicious code in @zalastax/nolb-node-w (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-w package is an npm module designed for specific functionalities within Node.js applications. It is utilized for various tasks, but recent findings have revealed that it contains malicious code, posing a significant security risk to users and their applications. The package's widespread use in the community makes it essential to address this vulnerability promptly.
Vulnerability Detail
The vulnerability in the @zalastax/nolb-node-w package stems from the inclusion of malicious code that can compromise the security of applications using this package. This code can lead to unauthorized access, data breaches, or other malicious activities. The issue was identified and reported by Amazon Inspector, highlighting the importance of vigilance when using third-party packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall @zalastax/nolb-node-wIf 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-w package from your project until a secure version is released. You can do this by executing the command: 'npm uninstall @zalastax/nolb-node-w'. This will help mitigate the risk while you seek alternatives or await a fix.
Conclusion
The discovery of malicious code in the @zalastax/nolb-node-w package highlights the critical need for developers to remain vigilant when using third-party packages. By updating to the latest version or removing the package, developers can protect their applications from potential threats. Utilizing tools like Vulert can further enhance security by providing real-time monitoring for vulnerabilities.
See every vulnerability recorded for @zalastax/nolb-node-w →
FAQ
The malicious code can lead to unauthorized access and potential data breaches, compromising the security of applications using this package.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check if your application is affected without needing to sign up.
If an immediate update is not possible, consider removing the package from your project as a temporary measure to mitigate risks.
The vulnerability was reported by Amazon Inspector, a security tool that helps identify vulnerabilities in software packages.
Yes, using tools like Vulert allows you to monitor your project for vulnerabilities in real-time, ensuring you are alerted to any issues as they arise.
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
