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

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

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-13763: Malicious code in @zalastax/nolb-react-sh (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-sh package is an npm library designed for React applications, providing specific functionalities that enhance the development experience. However, it has been identified to contain malicious code, posing significant risks to users and their applications. This vulnerability can lead to unauthorized access or manipulation of application data.

Vulnerability Detail

The vulnerability in the @zalastax/nolb-react-sh package stems from the inclusion of malicious code that can compromise the security of applications utilizing this library. The malicious code may allow attackers to execute arbitrary commands, steal sensitive information, or disrupt application functionality. This issue was introduced in version 0 and affects all subsequent versions.

How To Fix

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

npm uninstall @zalastax/nolb-react-sh

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, consider using alternative packages that provide similar functionality without the associated risks. Always review the package's security history before integrating it into your project.

Conclusion

The discovery of malicious code in the @zalastax/nolb-react-sh package highlights the importance of vigilant monitoring of open-source dependencies. Users are advised to remove the affected package and consider alternatives while keeping an eye on updates from the package maintainers.

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

Share this vulnerability

FAQ

The malicious code can execute unauthorized commands and potentially compromise sensitive data within applications.

You can use Vulert to monitor and alert for vulnerabilities in your software. By checking your package-lock.json file, Vulert can identify if your application is affected by this vulnerability.

If immediate removal is not possible, consider isolating the affected functionality and monitoring your application closely for any suspicious activity.

Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring any signup.

The impacts can range from data theft and unauthorized access to complete application compromise, which can severely affect user trust and application integrity.

How To Fix

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

npm uninstall @zalastax/nolb-react-sh

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