Malicious Code Detected in @zalastax/nolb-nodei Package
Summary
MAL-2025-12772: Malicious code in @zalastax/nolb-nodei (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-nodei package is an npm library designed for specific functionalities within Node.js applications. It is utilized by developers for its ease of integration and various features. However, it has been identified to contain malicious code, posing significant risks to applications that incorporate it.
Vulnerability Detail
The vulnerability in the @zalastax/nolb-nodei package stems from the inclusion of malicious code, which can compromise the security of applications using this package. This issue was introduced in version 0 and affects all subsequent versions. The malicious code could lead to unauthorized access, data breaches, or other harmful actions within the application environment.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall @zalastax/nolb-nodei
If 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 measure, you can avoid using the @zalastax/nolb-nodei package in your application until a safe version is released. Consider using alternative packages that provide similar functionality without the associated risks.
Conclusion
The discovery of malicious code in the @zalastax/nolb-nodei package highlights the importance of vigilance in managing open-source dependencies. Developers are advised to remove the package and seek alternatives to safeguard their applications.
See every vulnerability recorded for @zalastax/nolb-nodei →
FAQ
The malicious code can potentially allow unauthorized access and manipulation of the application, leading to security breaches.
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.
The best mitigation strategy is to remove the affected package and replace it with a secure alternative until a patched version is available.
Immediately remove the @zalastax/nolb-nodei package from your project and monitor for any updates or patches that may address the vulnerability.
Detailed information can be found on the GitHub repository of the malicious package, as well as through security advisories related to npm packages.