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

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

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-13710: Malicious code in @zalastax/nolb-react-pb (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-pb 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 it. This vulnerability can lead to unauthorized access or manipulation of application data.

Vulnerability Detail

The vulnerability stems from the inclusion of malicious code within the @zalastax/nolb-react-pb package. This code can execute harmful actions when the package is installed or used in a project, potentially compromising the security of the application and its users. The malicious nature of the code can lead to data breaches, unauthorized access, and other security incidents.

How To Fix

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

npm uninstall @zalastax/nolb-react-pb

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 measure, you can avoid using the @zalastax/nolb-react-pb package until a secure version is released. Additionally, consider using alternative packages that provide similar functionalities without the associated risks.

Conclusion

The discovery of malicious code in the @zalastax/nolb-react-pb package poses a serious risk to developers and users alike. Immediate action is required to mitigate potential threats by uninstalling the package and monitoring for updates. Utilizing tools like Vulert can help in identifying vulnerabilities in your applications.

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

Share this vulnerability

FAQ

The malicious code can execute harmful actions that compromise the security of applications using this package.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check if your application is affected without requiring any signup.

If you have installed the package, immediately uninstall it using 'npm uninstall @zalastax/nolb-react-pb' and look for alternative solutions.

While specific exploits have not been detailed, the presence of malicious code indicates potential for various attacks, including data breaches.

A fix will depend on the package maintainers. Keep an eye on the package repository for updates or patches.

How To Fix

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

npm uninstall @zalastax/nolb-react-pb

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