Malicious Code Detected in gixxcel Package - Security Alert

gixxcel Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-21498: Malicious code in gixxcel (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 Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The gixxcel package is an npm library that provides various functionalities for developers. However, it has been identified as containing malicious code, which poses significant security risks to applications that utilize this package. The presence of such code can lead to unauthorized access, data breaches, and other malicious activities.

Vulnerability Detail

The vulnerability stems from the inclusion of malicious code within the gixxcel package. This code can execute harmful operations without the user's consent, potentially compromising sensitive data and system integrity. The issue was introduced in version 0 of the package, and it is crucial for developers to be aware of the risks associated with using this compromised library.

How To Fix

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

npm uninstall gixxcel

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

If an immediate update is not possible, consider removing the gixxcel package from your project until a secure version is released. You can uninstall it using the command: npm uninstall gixxcel.

Conclusion

The gixxcel package has been identified as containing malicious code, posing serious security risks. It is essential for developers to update or remove the package to protect their applications. Utilizing tools like Vulert can help in monitoring and managing open-source vulnerabilities effectively.

See every vulnerability recorded for gixxcel →

Share this vulnerability

FAQ

gixxcel is an npm package designed to assist developers with various functionalities, but it has been compromised with malicious code.

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

If you cannot update the gixxcel package right away, consider removing it from your project to mitigate the risk until a secure version is available.

Using the compromised gixxcel package can lead to unauthorized access, data breaches, and other malicious activities that can harm your application and its users.

Utilize tools like Vulert to monitor your project's dependencies for vulnerabilities and receive real-time alerts.

How To Fix

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

npm uninstall gixxcel

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