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

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

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-13661: Malicious code in @zalastax/nolb-react-ab (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-ab package is an npm library designed for React applications, providing various functionalities for building user interfaces. However, it has been identified to contain malicious code, posing a significant security risk to applications that utilize it. Users of this package should be aware of its potential vulnerabilities and take immediate action to mitigate risks.

Vulnerability Detail

The vulnerability in the @zalastax/nolb-react-ab package stems from the inclusion of malicious code that can compromise the security of applications using this library. This code may lead to unauthorized access, data breaches, or other harmful actions within the affected systems. The issue was introduced in version 0 and affects all subsequent versions, 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-ab

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 replace the functionality provided by the @zalastax/nolb-react-ab package with alternative libraries that do not contain malicious code. Ensure to thoroughly review and test any new packages before integrating them into your application.

Conclusion

The discovery of malicious code in the @zalastax/nolb-react-ab package highlights the importance of vigilance in managing open-source dependencies. Users are urged to take immediate action by removing the affected package and exploring alternatives to safeguard their applications.

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

Share this vulnerability

FAQ

The malicious code can lead to unauthorized access and potential data breaches in applications that use this package.

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

Currently, there is no patched version available for the @zalastax/nolb-react-ab package. It is advisable to remove the package until a secure version is released.

You should immediately remove the @zalastax/nolb-react-ab package from your project and consider using alternative libraries.

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

How To Fix

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

npm uninstall @zalastax/nolb-react-ab

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