Critical Malicious Code Vulnerability in gboxghost Package

gboxghost Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-21229: Malicious code in gboxghost (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 gboxghost package is an npm library designed for specific functionalities within JavaScript applications. It is utilized for various tasks, but its integrity has been compromised due to the presence of malicious code. This vulnerability poses a significant risk to applications relying on this package, as it can lead to unauthorized access or data breaches.

Vulnerability Detail

The gboxghost package has been identified to contain malicious code that can be exploited by attackers. This vulnerability originated from the introduction of harmful scripts within the package, which can execute unauthorized actions on the host system. The ramifications of this vulnerability include potential data theft, system compromise, and the ability for attackers to manipulate application behavior. Users of the gboxghost package are at risk if they do not take immediate action to mitigate this threat.

How To Fix

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

npm uninstall gboxghost

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 removing the gboxghost package from your project until a secure version is confirmed. You can do this by executing: 'npm uninstall gboxghost'. This will prevent any potential exploitation while you assess the situation.

Conclusion

The gboxghost package has been found to contain malicious code, posing a significant risk to applications that utilize it. Users are advised to update to the latest patched version or remove the package until a secure version is confirmed. Utilizing tools like Vulert can help monitor and alert for such vulnerabilities in real-time.

See every vulnerability recorded for gboxghost →

Share this vulnerability

FAQ

gboxghost is an npm package used in JavaScript applications for specific functionalities, but it has been compromised with malicious code.

You can check if your application is affected by using Vulert, which monitors vulnerabilities in real-time. Visit Vulert Scanner to assess your application without needing to sign up.

The risks include unauthorized access to your system, data breaches, and manipulation of application behavior, which can lead to severe security incidents.

Yes, a patch is available. You can update the package to the latest secure version using 'npm update gboxghost'.

If an immediate update is not possible, consider uninstalling the gboxghost package to prevent exploitation until a secure version is available.

How To Fix

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

npm uninstall gboxghost

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