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

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

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-13794: Malicious code in @zalastax/nolb-react-t (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-t package is an npm library designed for React applications, providing various functionalities that enhance user interface components. However, it has been identified to contain malicious code, posing significant security risks to applications that utilize it. Developers relying on this package should be aware of its vulnerabilities and take immediate action to safeguard their projects.

Vulnerability Detail

The vulnerability in the @zalastax/nolb-react-t package arises from the inclusion of malicious code that can compromise the security of applications using this library. This malicious code can lead to unauthorized access, data breaches, or other harmful actions within the affected systems. The issue was introduced in version 0 and affects all subsequent versions, making it critical for users to address this vulnerability promptly.

How To Fix

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

npm uninstall @zalastax/nolb-react-t

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

Currently, there are no specific workarounds to mitigate the risks posed by the malicious code in the @zalastax/nolb-react-t package. The best approach is to uninstall the package and replace it with a secure alternative.

Conclusion

The discovery of malicious code in the @zalastax/nolb-react-t package underscores the importance of vigilance in managing open-source dependencies. Developers should take immediate action to remove this package and seek secure alternatives to protect their applications from potential threats.

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

Share this vulnerability

FAQ

The malicious code can compromise application security, potentially allowing unauthorized access or data breaches.

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

Immediately uninstall the @zalastax/nolb-react-t package and replace it with a secure alternative.

No patch is available for the @zalastax/nolb-react-t package as the malicious code is inherent to its current versions.

Regularly monitor your dependencies using tools like Vulert 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-t

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