Malicious Code Detected in @zalastax/nolb-react-pj - Security Alert

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

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-13717: Malicious code in @zalastax/nolb-react-pj (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 package @zalastax/nolb-react-pj is an npm library designed for React applications, providing various functionalities for developers. However, it has been identified to contain malicious code, posing a significant risk to applications that utilize it. This vulnerability can compromise the integrity of the software and potentially lead to unauthorized access or data breaches.

Vulnerability Detail

The vulnerability in the @zalastax/nolb-react-pj package stems from the inclusion of malicious code. This code can execute harmful actions within the user's environment, such as data exfiltration or unauthorized system access. The issue was introduced from version 0 and affects all subsequent versions. Users of this package are at risk of severe security breaches if they do not 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-pj

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 avoid using the @zalastax/nolb-react-pj package until a secure version is released. Consider using alternative packages that provide similar functionality without the associated risks.

Conclusion

The discovery of malicious code in the @zalastax/nolb-react-pj package poses a serious threat to users. Immediate action is required to mitigate risks, including uninstalling the package and monitoring for updates. Utilizing tools like Vulert can help in maintaining awareness of vulnerabilities in your software.

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

Share this vulnerability

FAQ

The malicious code can perform unauthorized actions, potentially leading to data breaches or system compromise.

You can use Vulert's playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.

You should uninstall the package immediately and monitor your application for any unusual activity.

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

Vulert uses your package-lock.json file to monitor and alert in real-time for open-source vulnerabilities in your software.

How To Fix

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

npm uninstall @zalastax/nolb-react-pj

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