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

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

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-13800: Malicious code in @zalastax/nolb-react-tc (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-tc package is a JavaScript library designed for use in React applications, providing various functionalities for component development. 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 or data breaches.

Vulnerability Detail

The vulnerability in the @zalastax/nolb-react-tc package arises from the inclusion of malicious code that can compromise the security of applications using this package. This code can potentially allow attackers to execute harmful actions, such as data theft or unauthorized access to user information. The issue was introduced in version 0 and affects all subsequent versions.

How To Fix

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

npm uninstall @zalastax/nolb-react-tc

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-react-tc package until a secure version is released. Consider using alternative packages that provide similar functionality without the associated risks.

Conclusion

The discovery of malicious code in the @zalastax/nolb-react-tc package highlights the importance of vigilance in managing open-source dependencies. It is essential to monitor for vulnerabilities and take immediate action to protect your applications.

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

Share this vulnerability

FAQ

The malicious code can execute unauthorized actions within applications, potentially leading to data breaches or security vulnerabilities.

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 requiring any signup.

If you have installed the @zalastax/nolb-react-tc package, it is crucial to remove it immediately and look for alternatives or wait for a patched version.

While specific exploits have not been detailed, the presence of malicious code indicates a high risk of exploitation by attackers.

Yes, removing the @zalastax/nolb-react-tc package will mitigate the risk associated with the malicious code, making your application safer.

How To Fix

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

npm uninstall @zalastax/nolb-react-tc

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