Malicious Code Detected in @zalastax/nolb-angular0 Package
Summary
MAL-2025-10662: Malicious code in @zalastax/nolb-angular0 (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-angular0 package is an npm library designed for Angular applications, providing various functionalities to enhance development. However, it has been identified to contain malicious code, posing significant security risks to applications that utilize it.
Vulnerability Detail
The vulnerability stems from the inclusion of malicious code within the @zalastax/nolb-angular0 package. This code can potentially compromise the security of applications, leading to unauthorized access, data breaches, or other malicious activities. The issue was introduced in version 0 and affects all subsequent versions.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall @zalastax/nolb-angular0
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 workaround, consider using alternative packages that provide similar functionalities without the associated risks. Review your project's dependencies and replace @zalastax/nolb-angular0 with a trusted library.
Conclusion
The @zalastax/nolb-angular0 package has been found to contain malicious code, posing a serious threat to applications that utilize it. Immediate action is required to mitigate risks, including removing the package and monitoring for updates. Utilizing tools like Vulert can help in maintaining the security of your software.
See every vulnerability recorded for @zalastax/nolb-angular0 →
FAQ
The malicious code can perform unauthorized actions within your application, potentially leading to data theft or system compromise.
You can use tools like Vulert to monitor and alert for vulnerabilities in your software. Check your package-lock.json file with Vulert's playground at Vulert Scanner.
Currently, there is no patched version available. It is advised to remove the package until a secure version is released.
If immediate removal is not possible, consider isolating the affected code and monitoring for unusual activity while seeking alternatives.
Regularly audit your dependencies, use tools like Vulert for real-time monitoring, and stay updated on security advisories related to the packages you use.