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

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

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-13715: Malicious code in @zalastax/nolb-react-ph (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-ph package is an npm library designed for React applications, providing various functionalities to enhance user interfaces. However, it has been identified to contain malicious code, posing significant risks to applications that utilize it. Users of this package should be aware of its potential vulnerabilities and take necessary precautions.

Vulnerability Detail

The vulnerability stems from the inclusion of malicious code within the @zalastax/nolb-react-ph package. This code can lead to unauthorized access, data breaches, or other harmful actions within applications that depend on this package. The malicious nature of the code was confirmed by security researchers, highlighting the importance of vigilance when using third-party libraries.

How To Fix

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

npm uninstall @zalastax/nolb-react-ph

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 measure, consider replacing the functionality provided by @zalastax/nolb-react-ph with alternative libraries that do not have known vulnerabilities. Review your application’s dependencies and ensure that you are using secure and well-maintained packages.

Conclusion

The discovery of malicious code in the @zalastax/nolb-react-ph package underscores the importance of scrutinizing third-party libraries. Users should take immediate action to remove the package and consider alternatives to safeguard their applications. Utilizing tools like Vulert can help monitor for vulnerabilities in real-time.

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

Share this vulnerability

FAQ

The malicious code can potentially compromise application security, leading to unauthorized access or data manipulation.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software. Visit Vulert Scanner to check your application without requiring any signup.

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

Immediately remove the package from your project and consider using alternative libraries. Monitor your application for any unusual activity.

Regularly audit your dependencies, use tools like Vulert for real-time monitoring, and stay updated on security advisories related to the packages you use.

How To Fix

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

npm uninstall @zalastax/nolb-react-ph

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