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

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

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-13664: Malicious code in @zalastax/nolb-react-ae (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-ae package is a JavaScript library designed for use with React applications, providing various functionalities that enhance user interface components. However, it has been identified to contain malicious code, posing a significant security risk to applications that utilize this package.

Vulnerability Detail

The vulnerability originates from the inclusion of malicious code within the @zalastax/nolb-react-ae 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 the initial release, making it imperative for users to take immediate action.

How To Fix

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

npm uninstall @zalastax/nolb-react-ae

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 remove the @zalastax/nolb-react-ae package from your project until a secure version is released. This can be done using the command: npm uninstall @zalastax/nolb-react-ae.

Conclusion

The discovery of malicious code in the @zalastax/nolb-react-ae package poses a serious threat to applications using it. Immediate action is required to mitigate risks, including updating or removing the package. Users should remain vigilant and utilize tools like Vulert for ongoing monitoring.

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

Share this vulnerability

FAQ

The malicious code can perform unauthorized actions within the application, potentially compromising user data and application integrity.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software. Check your application using the Vulert playground at Vulert Scanner.

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

If immediate removal is not possible, ensure to monitor your application closely for any unusual behavior and consider implementing additional security measures.

Regularly check for updates in your dependencies and use tools like Vulert to receive real-time alerts for any vulnerabilities.

How To Fix

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

npm uninstall @zalastax/nolb-react-ae

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