Malicious Code Detected in @zalastax/nolb-angularh Package
Summary
MAL-2025-10664: Malicious code in @zalastax/nolb-angularh (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-angularh package is an npm library designed for Angular applications, providing various functionalities to enhance user interfaces. However, this package has been identified as containing malicious code, posing significant security risks to applications that utilize it. Users of this package should be aware of its potential vulnerabilities and take immediate action to protect their projects.
Vulnerability Detail
The vulnerability in the @zalastax/nolb-angularh package stems from the inclusion of malicious code that can compromise the security of applications using this library. This malicious code can lead to unauthorized access, data breaches, or other harmful actions within the affected applications. The issue was introduced in version 0 and affects all subsequent versions, making it critical for users to address this vulnerability promptly.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall @zalastax/nolb-angularhIf 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 workaround, you can remove the @zalastax/nolb-angularh package from your project by executing the following command: npm uninstall @zalastax/nolb-angularh. This will prevent the malicious code from executing in your application until a secure version is available.
Conclusion
The @zalastax/nolb-angularh package has been identified as containing malicious code, which poses a significant risk to applications that utilize it. Users are strongly advised to update or remove the package to safeguard their projects. Continuous monitoring with tools like Vulert can help maintain the security of your software.
See every vulnerability recorded for @zalastax/nolb-angularh →
FAQ
The malicious code can potentially allow unauthorized access to sensitive data or enable harmful actions within applications using the package.
You can use Vulert to monitor and alert for open-source vulnerabilities in your software. By utilizing the Vulert playground, you can check if your application is affected without any signup.
If an immediate update is not possible, consider removing the package from your project as a temporary measure to mitigate risks.
Yes, using Vulert, you can monitor your project for vulnerabilities in real-time by analyzing your package-lock.json file.
Detailed information about this vulnerability can be found in the Open Source Vulnerability database and on the GitHub repository for malicious packages.
