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

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

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-13735: Malicious code in @zalastax/nolb-react-rf (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-rf package is a JavaScript library designed for use with React applications, providing functionalities that enhance the development experience. However, it has been found to contain malicious code, posing a significant risk to users who integrate it into their projects. This vulnerability can lead to unauthorized access or manipulation of application data.

Vulnerability Detail

The vulnerability originates from the inclusion of malicious code within the @zalastax/nolb-react-rf package. This code can compromise the security of applications that utilize this package, potentially leading to data breaches or unauthorized actions within the application. The malicious nature of the code means that it can execute harmful operations without the user's consent, making it critical for developers to address this issue promptly.

How To Fix

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

npm uninstall @zalastax/nolb-react-rf

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 possible, consider removing the package from your project until a secure version is released. You can uninstall the package using the command: npm uninstall @zalastax/nolb-react-rf.

Conclusion

The discovery of malicious code in the @zalastax/nolb-react-rf package highlights the importance of regularly updating dependencies and monitoring for vulnerabilities. Users are advised to take immediate action to secure their applications by updating or removing the affected package.

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

Share this vulnerability

FAQ

The malicious code can execute unauthorized operations, potentially compromising application security and user data.

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

Consider removing the package from your project until a secure version is available to prevent potential security risks.

Yes, tools like Vulert can help you monitor and alert you in real-time for open-source vulnerabilities using just your package-lock.json.

Using a vulnerable package can lead to data breaches, unauthorized access, and other security incidents that can harm your application and its users.

How To Fix

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

npm uninstall @zalastax/nolb-react-rf

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