Critical Malicious Code Vulnerability in @bellaxchuu/xbails Package

@bellaxchuu/xbails Updated 08 Oct 2026

Summary

08/10/2026
CRITICAL
No i
Critical
Not published

MAL-2026-17679: Malicious code in @bellaxchuu/xbails (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/xbails package is an npm library that is designed to provide specific functionalities for JavaScript applications. However, it has been identified as containing malicious code that compromises the security of any system where it is installed. This vulnerability poses a significant risk to developers and organizations relying on this package for their projects.

Vulnerability Detail

The vulnerability originates from the inclusion of malicious code within the @bellaxchuu/xbails package. Any computer that has this package installed is considered fully compromised, as it may grant unauthorized access to sensitive information, including secrets and keys stored on that machine. The malicious code can lead to severe ramifications, including data breaches and loss of control over the affected systems.

How To Fix

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

npm uninstall @bellaxchuu/xbails

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

Currently, there are no effective workarounds to mitigate the risks associated with this vulnerability. The only recommended action is to remove the package entirely from your project.

Conclusion

The @bellaxchuu/xbails package has been identified as containing malicious code that compromises the security of any system where it is installed. Immediate action is required to uninstall the package and secure any sensitive information. Regular monitoring of dependencies is essential to prevent similar vulnerabilities in the future.

See every vulnerability recorded for @bellaxchuu/xbails →

Share this vulnerability

FAQ

You should immediately uninstall the package using 'npm uninstall @bellaxchuu/xbails' and rotate any sensitive information stored on the affected system.

You can use the Vulert platform to monitor and alert for open-source vulnerabilities in your software. Visit Vulert Scanner to check your application without any signup.

Keeping the @bellaxchuu/xbails package installed can lead to unauthorized access to your system, data breaches, and potential loss of sensitive information.

Regularly monitor your dependencies for vulnerabilities using tools like Vulert, which can alert you in real-time for open-source vulnerabilities.

It is advisable to review and verify the security of other packages from the same author before using them, especially after encountering a malicious package.

How To Fix

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

npm uninstall @bellaxchuu/xbails

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