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

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

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-13779: Malicious code in @zalastax/nolb-react-std (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 Penetration testing for web, API and mobile 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-std package is a JavaScript library designed for use in React applications, providing standard functionalities for building user interfaces. It is part of the npm ecosystem, which is widely used for managing JavaScript packages. However, this package has been identified to contain malicious code, posing significant risks to applications that utilize it.

Vulnerability Detail

The vulnerability in the @zalastax/nolb-react-std package stems from the inclusion of malicious code that can compromise the security of applications using this library. This code could potentially lead to unauthorized access, data breaches, or other harmful actions within the application. The malicious code was introduced in version 0 and has been confirmed by security researchers.

How To Fix

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

npm uninstall @zalastax/nolb-react-std

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 an alternative package that provides similar functionalities without the associated risks. Review your project's dependencies and replace @zalastax/nolb-react-std with a trusted library.

Conclusion

The @zalastax/nolb-react-std package has been identified as containing malicious code, which poses significant risks to applications. It is essential to uninstall this package and monitor for updates or alternatives to ensure the security of your application.

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

Share this vulnerability

FAQ

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

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

Immediately uninstall the package using 'npm uninstall @zalastax/nolb-react-std' and consider using an alternative library.

Currently, there is no patched version available. It is recommended to remove the package until a secure version is released.

Regularly monitor your dependencies for vulnerabilities using tools like Vulert and keep your packages updated to their latest versions.

How To Fix

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

npm uninstall @zalastax/nolb-react-std

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