Malicious Code Detected in gbiz-next Package - Version 2.3.19

gbiz-next Updated 21 Nov 2025

Summary

18/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-190573: Malicious code in gbiz-next (npm). Affects gbiz-next versions 2.3.19. 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 gbiz-next package is a Node.js library used in various applications for its functionalities related to business operations. It is designed to streamline processes and enhance productivity. However, version 2.3.19 has been flagged for malicious behavior, raising concerns about its integrity and safety for users.

Vulnerability Detail

The vulnerability in the gbiz-next package arises from its ability to execute commands associated with malicious behavior. This was identified by the OpenSSF Package Analysis project, which determined that the package could potentially compromise the security of applications using it. The malicious code could lead to unauthorized access, data breaches, or other harmful actions within the affected systems.

How To Fix

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

npm uninstall gbiz-next

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, users can avoid using the gbiz-next package altogether until a secure version is confirmed. If the package is essential, consider isolating its usage in a controlled environment to minimize potential risks.

Conclusion

The gbiz-next package version 2.3.19 has been identified as malicious, posing significant risks to applications that utilize it. Users are advised to update to a secure version and consider using tools like Vulert for ongoing monitoring of vulnerabilities in their software.

See every vulnerability recorded for gbiz-next →

Share this vulnerability

FAQ

gbiz-next is a Node.js library used for various business-related functionalities in applications.

Version 2.3.19 has been flagged for executing commands that can lead to malicious behavior, compromising application security.

You can use Vulert to monitor and alert for open-source vulnerabilities in your software. Visit Vulert Scanner to check if your application is affected without needing to sign up.

As a workaround, consider isolating the usage of the gbiz-next package in a controlled environment to reduce potential risks until an update can be applied.

You can refer to the OpenSSF Package Analysis project or use tools like Vulert to stay informed about vulnerabilities in open-source packages.

How To Fix

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

npm uninstall gbiz-next

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