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

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

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-13820: Malicious code in @zalastax/nolb-react-ty (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-ty package is an npm library designed for React applications, providing various functionalities to enhance user interfaces. However, it has been identified to contain malicious code, posing a significant security risk to applications that utilize it. This vulnerability can compromise the integrity of the software and potentially lead to unauthorized access or data breaches.

Vulnerability Detail

The vulnerability originates from the inclusion of malicious code within the @zalastax/nolb-react-ty package. This code can execute harmful actions without the user's consent, potentially leading to data theft, system compromise, or other malicious activities. The issue affects all versions of the package starting from its introduction, making it critical for users to address this vulnerability immediately.

How To Fix

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

npm uninstall @zalastax/nolb-react-ty

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 removing the @zalastax/nolb-react-ty package from your project until a secure version is released. You can do this by executing the following command: npm uninstall @zalastax/nolb-react-ty.

Conclusion

The @zalastax/nolb-react-ty package has been found to contain malicious code, posing a serious security threat to applications that utilize it. Users are urged to uninstall the package and monitor for updates. Utilizing tools like Vulert can help in identifying and managing such vulnerabilities effectively.

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

Share this vulnerability

FAQ

The malicious code can perform unauthorized actions, potentially leading to data breaches or system compromises.

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.

Currently, there is no specific patch version available for the @zalastax/nolb-react-ty package. Users are advised to uninstall the package until a secure version is released.

It is recommended to uninstall the package immediately and monitor for any updates or patches that may address the vulnerability.

Vulert uses the package-lock.json file to monitor and alert users in real-time for open-source vulnerabilities, ensuring that your software remains secure.

How To Fix

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

npm uninstall @zalastax/nolb-react-ty

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