Malicious Code Detected in @zalastax/nolb-api-u Package

@zalastax/nolb-api-u Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-10683: Malicious code in @zalastax/nolb-api-u (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-api-u package is an npm library designed for API interactions. It is utilized by developers to streamline backend communication in applications. However, this package has been identified to contain malicious code, posing a significant risk to users and their applications.

Vulnerability Detail

The vulnerability arises from the presence of malicious code within the @zalastax/nolb-api-u package. This code can potentially lead to unauthorized access, data breaches, or other harmful actions within the applications that utilize this package. The malicious nature of the code was confirmed through security assessments, indicating that any version of the package from its introduction is affected.

How To Fix

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

npm uninstall @zalastax/nolb-api-u

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, you can avoid using the @zalastax/nolb-api-u package altogether and seek alternative libraries that provide similar functionality without the associated risks.

Conclusion

The @zalastax/nolb-api-u package has been identified as containing malicious code, posing serious security risks to applications that utilize it. Immediate action is required to remove the package and seek alternatives to safeguard your application.

See every vulnerability recorded for @zalastax/nolb-api-u →

Share this vulnerability

FAQ

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

You can use Vulert's playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.

It is advised to remove the package immediately and look for alternative solutions.

As of now, there is no patched version available. Monitor the official repository for updates.

Continuing to use this package exposes your application to potential security threats, including data theft and unauthorized access.

How To Fix

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

npm uninstall @zalastax/nolb-api-u

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