Critical Malicious Code Vulnerability in @zalastax/nolb-hap_ Package
Summary
MAL-2025-11916: Malicious code in @zalastax/nolb-hap_ (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-hap_ package is a Node.js library designed for handling HTTP requests in a highly efficient manner. It is often utilized in web applications to facilitate load balancing and improve performance. However, recent findings have revealed that this package contains malicious code, posing significant risks to users and their applications.
Vulnerability Detail
The vulnerability stems from the inclusion of malicious code within the @zalastax/nolb-hap_ package. This code can potentially compromise the integrity of applications using this package, leading to unauthorized access, data breaches, or other malicious activities. The issue affects all versions starting from 0, making it critical 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-hap_
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 workaround, users can remove the @zalastax/nolb-hap_ package from their project to prevent any potential exploitation of the malicious code. This can be done using the following command: npm uninstall @zalastax/nolb-hap_.
Conclusion
The discovery of malicious code in the @zalastax/nolb-hap_ package highlights the importance of vigilance in managing open-source dependencies. Users are urged to take immediate action by updating or removing the package to safeguard their applications.
See every vulnerability recorded for @zalastax/nolb-hap_ →
FAQ
The malicious code is designed to compromise the security of applications using the package, potentially leading to unauthorized access and data breaches.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. You can check your application using the Vulert playground without any signup.
If you cannot update the package, it is advisable to remove it from your project until a secure version is released.
Currently, all versions starting from 0 are affected. Users should wait for a patched version to be released.
You can follow the official repository of the package on GitHub or subscribe to vulnerability alert services like Vulert for real-time updates.