Malicious Code Detected in @zalastax/nolb-angular_: A Critical Security Concern
Summary
MAL-2025-10663: Malicious code in @zalastax/nolb-angular_ (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 package @zalastax/nolb-angular_ is an npm library designed for Angular applications, providing various functionalities to enhance user interfaces. However, it has been identified to contain malicious code, posing significant security risks to applications that utilize it. This vulnerability can lead to unauthorized access or data breaches, making it crucial for developers to address it promptly.
Vulnerability Detail
The vulnerability in the @zalastax/nolb-angular_ package stems from the inclusion of malicious code that can compromise the security of applications using this library. The malicious code can potentially allow attackers to execute unauthorized actions, access sensitive data, or disrupt application functionality. This issue was introduced in version 0 and affects all subsequent versions, making it imperative for users to take immediate action to mitigate risks.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall @zalastax/nolb-angular_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 remove the @zalastax/nolb-angular_ package from your project to prevent any potential exploitation of the vulnerability. This can be done using the following command: npm uninstall @zalastax/nolb-angular_.
Conclusion
The discovery of malicious code in the @zalastax/nolb-angular_ package presents a serious security threat to applications utilizing this library. Developers are urged to take immediate action by updating or removing the package to safeguard their applications against potential exploits.
See every vulnerability recorded for @zalastax/nolb-angular_ →
FAQ
The malicious code can execute unauthorized actions and access sensitive data within applications that use this package.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software. Simply upload your package-lock.json file to check for vulnerabilities.
Yes, you can mitigate risks by updating to a patched version of the package or removing it from your project until a secure version is available.
If no patched version is available, it is advisable to remove the package from your project to avoid potential security risks.
Yes, using the Vulert playground, you can check if your application is affected by vulnerabilities without needing to sign up or access the code.
