Malicious Code Detected in @zalastax/nolb-node-y Package
Summary
MAL-2025-12705: Malicious code in @zalastax/nolb-node-y (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-y package is a Node.js library designed for specific functionalities within the npm ecosystem. It is utilized by developers to streamline certain tasks in their applications. However, this package has been identified as containing malicious code, posing significant risks to users who integrate it into their projects.
Vulnerability Detail
The vulnerability in the @zalastax/nolb-node-y 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 harmful actions within the affected systems. The malicious nature of the code was discovered by Amazon Inspector, highlighting the importance of scrutinizing third-party packages before use.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall @zalastax/nolb-node-yIf 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, consider using alternative packages that offer similar functionality without the associated risks. Always ensure to review the security of any package before integration.
Conclusion
The discovery of malicious code in the @zalastax/nolb-node-y package underscores the critical need for vigilance when using third-party libraries. Users are advised to remove the package and monitor their applications for vulnerabilities to maintain security.
See every vulnerability recorded for @zalastax/nolb-node-y →
FAQ
The malicious code can lead to unauthorized access and potential data breaches.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time using just your package-lock.json file.
Immediately uninstall the package and look for alternatives or a patched version.
Yes, you can use the Vulert playground to check if your application is affected by this vulnerability without any signup.
Using compromised packages can lead to security breaches, data loss, and damage to your application's integrity.
