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

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

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-13725: Malicious code in @zalastax/nolb-react-pt (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 Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

The @zalastax/nolb-react-pt package is an npm library designed for React applications, providing specific functionalities that enhance user interface components. However, it has been identified to contain malicious code, posing a significant security risk to applications that utilize it. This vulnerability can lead to unauthorized access or data breaches, making it crucial for developers to address it promptly.

Vulnerability Detail

The vulnerability in the @zalastax/nolb-react-pt package originates from the inclusion of malicious code within its codebase. This malicious code can execute harmful actions, such as data exfiltration or unauthorized access to user information. The potential ramifications include compromised application integrity, loss of user trust, and legal implications for data breaches. It is essential for developers to be aware of this vulnerability and take immediate action to mitigate its impact.

How To Fix

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

npm uninstall @zalastax/nolb-react-pt

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-pt package from your project by executing the following command: npm uninstall @zalastax/nolb-react-pt. This will prevent the execution of the malicious code until a fix is provided.

Conclusion

The discovery of malicious code in the @zalastax/nolb-react-pt package poses a serious threat to applications utilizing this library. Developers must take immediate action to mitigate risks by updating or removing the package. Utilizing tools like Vulert can help monitor for vulnerabilities and ensure application security.

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

Share this vulnerability

FAQ

The malicious code can perform unauthorized actions, potentially leading to data breaches or loss of user information.

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

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

Failure to address this vulnerability can lead to compromised application security, data breaches, and loss of user trust.

Immediately uninstall the package and monitor your application for any unusual activity. Consider using alternative packages that provide similar functionality.

How To Fix

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

npm uninstall @zalastax/nolb-react-pt

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