Malicious Code Detected in @zalastax/nolb-react-tb: A Critical Security Concern

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

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-13799: Malicious code in @zalastax/nolb-react-tb (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 package @zalastax/nolb-react-tb is an npm library designed for React applications, providing various functionalities for building user interfaces. However, it has been identified to contain malicious code, posing significant security risks to applications that utilize it. This vulnerability can lead to unauthorized access, data breaches, and other malicious activities.

Vulnerability Detail

The vulnerability in @zalastax/nolb-react-tb stems from the inclusion of malicious code within the package. This code can execute harmful actions when the package is used in applications, potentially compromising user data and application integrity. The issue was introduced from version 0 and remains unaddressed in the current release, making it imperative for developers 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-react-tb

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 functionalities without the associated risks. Review your application's dependencies and ensure that you are not relying on compromised packages.

Conclusion

The discovery of malicious code in the @zalastax/nolb-react-tb package highlights the importance of vigilance in managing open-source dependencies. Developers must take immediate action to remove the affected package and consider alternatives to safeguard their applications from potential threats.

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

Share this vulnerability

FAQ

The malicious code can perform unauthorized actions, potentially leading to data breaches and security vulnerabilities in applications.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check your application without any signup.

Immediately uninstall the package using 'npm uninstall @zalastax/nolb-react-tb' and look for alternative packages to replace its functionality.

Currently, there is no patch available. It is crucial to monitor the package repository for any updates regarding a fix.

Regularly audit your dependencies, use tools like Vulert for monitoring, and stay updated on security advisories related to 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-react-tb

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