Malicious Code Detected in @zalastax/nolb-parse3 Package

@zalastax/nolb-parse3 Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-12977: Malicious code in @zalastax/nolb-parse3 (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 MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

The @zalastax/nolb-parse3 package is an npm library designed for parsing network load balancer configurations. It is utilized by developers to streamline the management of load balancer settings in their applications. However, this package has been found to contain malicious code, posing significant security risks to users who integrate it into their projects.

Vulnerability Detail

The vulnerability originates from the inclusion of malicious code within the @zalastax/nolb-parse3 package. This code can potentially compromise the integrity of applications that rely on 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 address it promptly.

How To Fix

This package is malicious. Remove it and rotate any credentials it could have accessed.

npm uninstall @zalastax/nolb-parse3

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 assess whether you can replace @zalastax/nolb-parse3 with a safer option.

Conclusion

The discovery of malicious code in the @zalastax/nolb-parse3 package poses a serious threat to applications that utilize it. Users are urged to remove the package immediately and consider alternatives to safeguard their projects. Staying informed about vulnerabilities and utilizing monitoring tools like Vulert can help maintain the security of your software.

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

Share this vulnerability

FAQ

The malicious code can lead to unauthorized access and potential data breaches within applications that utilize 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 any signup.

If immediate removal is not possible, consider implementing strict access controls and monitoring for any suspicious activity in your application.

While specific exploits have not been detailed, the presence of malicious code indicates a high risk of exploitation, making it imperative to address the issue.

Regularly check for updates in your dependencies and utilize tools like Vulert to receive real-time alerts for any vulnerabilities.

How To Fix

This package is malicious. Remove it and rotate any credentials it could have accessed.

npm uninstall @zalastax/nolb-parse3

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