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

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

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-13747: Malicious code in @zalastax/nolb-react-rt (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 Devnack Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The @zalastax/nolb-react-rt package is an npm library designed for React applications, providing functionalities that enhance the development experience. However, it has been identified to contain malicious code, posing a significant risk to applications that utilize this package.

Vulnerability Detail

The vulnerability originates from the inclusion of malicious code within the @zalastax/nolb-react-rt package. This code can potentially compromise the security of applications using this package, leading to unauthorized access, data breaches, or other malicious activities. The issue affects all versions starting from 0, 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-rt

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

If an immediate update is not feasible, consider removing the package from your project until a secure version is released. You can do this by executing: npm uninstall @zalastax/nolb-react-rt.

Conclusion

The discovery of malicious code in the @zalastax/nolb-react-rt package highlights the importance of maintaining secure dependencies in software development. Users are urged to update or remove the affected package to mitigate risks.

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

Share this vulnerability

FAQ

The malicious code is designed to exploit vulnerabilities in applications, potentially leading to unauthorized access or data theft.

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.

As a temporary measure, consider uninstalling the package until a secure version is available.

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

Regularly check your dependencies for updates and utilize tools like Vulert to receive real-time alerts on vulnerabilities.

How To Fix

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

npm uninstall @zalastax/nolb-react-rt

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