Critical Malicious Code Vulnerability in @bellaxchuu/xbailey Package

@bellaxchuu/xbailey Updated 08 Oct 2026

Summary

08/10/2026
CRITICAL
No i
Critical
Not published

MAL-2026-17678: Malicious code in @bellaxchuu/xbailey (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 @bellaxchuu/xbailey package is an npm library that is used for various functionalities within JavaScript applications. It is designed to facilitate certain tasks, but it has been found to contain malicious code that compromises the security of any system where it is installed. This vulnerability poses a significant risk to users and systems relying on this package.

Vulnerability Detail

The vulnerability originates from the presence of embedded malicious code within the @bellaxchuu/xbailey package. This code can fully compromise any computer that has the package installed, allowing unauthorized access to sensitive information such as secrets and keys. The ramifications of this vulnerability are severe, as it may lead to data breaches and loss of control over the affected systems. Users are advised to treat any system with this package as compromised.

How To Fix

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

npm uninstall @bellaxchuu/xbailey

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

There are no effective workarounds for this vulnerability other than removing the package entirely. Ensure that you monitor your systems for any unusual activity following the removal.

Conclusion

The @bellaxchuu/xbailey package contains malicious code that poses a serious security threat. Immediate action is required to remove the package and secure any compromised systems. Users should remain vigilant and utilize tools like Vulert to monitor for future vulnerabilities.

See every vulnerability recorded for @bellaxchuu/xbailey →

Share this vulnerability

FAQ

You should immediately uninstall the package and rotate any sensitive information stored on the affected system.

You can use the Vulert playground at Vulert Scanner to check if your application is affected without requiring any signup.

The risks include unauthorized access to sensitive information, potential data breaches, and loss of control over your systems.

No, there is currently no patched version available for the @bellaxchuu/xbailey package. The only solution is to remove it.

You can use Vulert, which monitors and alerts you in real-time for open-source vulnerabilities using just your package-lock.json file.

How To Fix

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

npm uninstall @bellaxchuu/xbailey

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