Malicious Code Detected in @zalastax/nolb-angulari Package
Summary
MAL-2025-10665: Malicious code in @zalastax/nolb-angulari (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-angulari package is an npm library designed for Angular applications, providing various functionalities that enhance the development experience. However, it has been identified to contain malicious code, posing a significant security risk to users who integrate it into their projects.
Vulnerability Detail
The vulnerability originates from the inclusion of malicious code within the @zalastax/nolb-angulari package. This code can potentially compromise the security of applications that utilize this package, leading to unauthorized access, data breaches, or other harmful effects. The malicious nature of the code makes it imperative for developers to act swiftly to mitigate risks associated with its use.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall @zalastax/nolb-angulariIf 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 removing the @zalastax/nolb-angulari package from your project until a secure version is released. You can do this by running the command: npm uninstall @zalastax/nolb-angulari.
Conclusion
The discovery of malicious code in the @zalastax/nolb-angulari package highlights the importance of vigilance in managing open-source dependencies. Developers are urged to take immediate action to protect their applications and data by removing the affected package and staying informed about security updates.
See every vulnerability recorded for @zalastax/nolb-angulari →
FAQ
The malicious code can lead to unauthorized access and potential data breaches in applications that use this package.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check your application without needing to sign up.
Yes, the best way to mitigate risks is to uninstall the affected package and monitor for any updates or patches that address the vulnerability.
Immediately remove the package and assess your application for any potential security breaches or unauthorized access.
Consider looking for other reputable Angular packages that provide similar functionalities without the associated risks.
