Malicious Code Detected in baes-x Package - Security Alert

baes-x Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-15333: Malicious code in baes-x (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 Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The baes-x package is an npm library designed for specific functionalities within JavaScript applications. It is utilized for various purposes, including data manipulation and API interactions. However, this package has been identified with a serious security vulnerability that exposes users to potential risks, including unauthorized access and data breaches.

Vulnerability Detail

The baes-x package contains malicious code that can compromise the security of applications using it. This vulnerability originated from the package itself, which was found to have been tampered with to include harmful scripts. The ramifications of this vulnerability can include data theft, unauthorized system access, and exploitation of the affected systems. Developers using this package should be aware of the risks associated with its use and take immediate action to mitigate potential threats.

How To Fix

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

npm uninstall baes-x

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, you can remove the baes-x package from your project until a secure version is released. Use the following command to uninstall the package: npm uninstall baes-x. This will help mitigate the risk of exposure while you await a fix.

Conclusion

The discovery of malicious code in the baes-x package poses a serious threat to applications that utilize it. Developers are urged to take immediate action by updating or removing the package to safeguard their systems. Utilizing tools like Vulert can further enhance security by providing real-time alerts for vulnerabilities.

See every vulnerability recorded for baes-x →

Share this vulnerability

FAQ

The baes-x package is an npm library used in JavaScript applications for various functionalities, including data manipulation.

The malicious code in baes-x can lead to unauthorized access and data breaches, posing significant security risks.

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 any signup.

If you cannot update the package, it is advisable to uninstall it temporarily to reduce the risk of exposure until a secure version is available.

You can utilize tools like Vulert, which provides real-time monitoring for vulnerabilities in your software dependencies.

Related vulnerabilities

Recent vulnerabilities recorded for baes-x.

How To Fix

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

npm uninstall baes-x

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