Malicious Code Detected in @zalastax/nolb-react-uv Package

@zalastax/nolb-react-uv Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-13843: Malicious code in @zalastax/nolb-react-uv (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-react-uv package is a JavaScript library designed for use in React applications, providing utilities for managing user interfaces. It is utilized by developers for its ease of integration and functionality. However, it has been found to contain malicious code, posing significant risks to applications that rely on it.

Vulnerability Detail

The vulnerability in the @zalastax/nolb-react-uv package originates from the inclusion of malicious code that can compromise the security of applications using this package. This malicious code can lead to unauthorized access, data breaches, and potential exploitation of the affected systems. The issue affects all versions starting from 0, making it critical for users to take immediate action.

How To Fix

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

npm uninstall @zalastax/nolb-react-uv

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 workaround, developers can consider using alternative packages that offer similar functionality without the associated risks. Additionally, ensure that your application is monitored for vulnerabilities using tools like Vulert, which can alert you to any open-source vulnerabilities in real-time.

Conclusion

The discovery of malicious code in the @zalastax/nolb-react-uv package poses a significant threat to applications utilizing this library. Immediate action is required to mitigate risks, including removing the package and monitoring for updates or alternatives. Utilizing tools like Vulert can enhance your security posture by providing real-time alerts for vulnerabilities.

See every vulnerability recorded for @zalastax/nolb-react-uv →

Share this vulnerability

FAQ

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

You can use the Vulert playground at Vulert Scanner to check if your application is affected without needing to sign up.

You should remove the package from your project and look for alternative libraries or wait for a patched version.

As of now, there is no patch available. Users should monitor the official repository for updates.

Vulert uses your package-lock.json file to monitor and alert you in real-time for open-source vulnerabilities in your software.

How To Fix

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

npm uninstall @zalastax/nolb-react-uv

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