Malicious Code Detected in @zalastax/nolb-hap- Package

@zalastax/nolb-hap- Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-11914: Malicious code in @zalastax/nolb-hap- (npm). Affected versions are not published. No fix is published. How to fix ↓

Free scan

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.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

The @zalastax/nolb-hap- package is an npm library designed for handling HTTP requests in Node.js applications. It aims to provide developers with a simplified interface for managing load balancers and routing. However, this package has been flagged for containing malicious code, which poses a significant risk to applications that utilize it.

Vulnerability Detail

The vulnerability in the @zalastax/nolb-hap- package stems from the inclusion of malicious code that can compromise the security of applications using this library. This code may lead to unauthorized access, data breaches, or other harmful actions within the affected systems. The malicious nature of this vulnerability was identified by Amazon Inspector, highlighting the importance of scrutinizing third-party packages for security 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, consider using alternative packages that provide similar functionality without the associated risks. Review your application's dependencies and ensure that you are not relying on compromised libraries.

Conclusion

The discovery of malicious code in the @zalastax/nolb-hap- package underscores the importance of vigilance when using third-party libraries. By promptly addressing this vulnerability and utilizing tools like Vulert, developers can enhance the security of their applications.

See every vulnerability recorded for @zalastax/nolb-hap- →

Share this vulnerability

FAQ

The malicious code can lead to unauthorized access and potential data breaches in applications that use this package.

You can use Vulert to monitor and alert for open-source vulnerabilities in your software. Visit Vulert Scanner to check if your application is affected without needing to sign up.

Immediately uninstall the package using 'npm uninstall @zalastax/nolb-hap-' and look for alternative solutions.

While specific exploits have not been detailed, the presence of malicious code indicates a high risk of exploitation.

Regularly audit your dependencies, use tools like Vulert for real-time monitoring, and stay updated on security advisories for the packages you use.

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 →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback