Malicious Package in baes-x - Cryptocurrency Wallet Exfiltration

baes-x Updated 02 Oct 2025

Summary

04/09/2020
CRITICAL
No i
Critical
9.1

GHSA-2jm5-2cqf-6vw9: Malicious Package in baes-x. Affects baes-x versions >= 0.0.0. 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 baes-x package is an npm package that is used for [provide brief description of the package functionality]. It is vulnerable to a critical security issue that allows the installation of a malicious package containing malware. This malware is specifically designed to find and exfiltrate cryptocurrency wallets from the compromised computer.

Vulnerability Detail

The vulnerability in the baes-x package allows an attacker to install a malicious package that can compromise the security of the computer. Once installed, the malware searches for cryptocurrency wallets and exfiltrates them, potentially leading to financial loss for the user. It is important to note that any computer with this package installed or running should be considered fully compromised. Immediate action is required to rotate all secrets and keys stored on the affected computer from a different, secure computer. Removing the package may not guarantee the removal of all malicious software, as the attacker may have gained full control of the compromised computer.

How To Fix

No fixed version is published for this vulnerability.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Workaround

There is no known workaround for this vulnerability. It is crucial to follow the recommended steps to fix the issue and mitigate any potential damage caused by the malware.

Conclusion

The baes-x package is vulnerable to a critical security issue that allows the installation of a malicious package designed to exfiltrate cryptocurrency wallets. Any computer with this package installed or running should be considered fully compromised. Immediate action is required to rotate all secrets and keys stored on the affected computer from a different, secure computer. Removing the package may not guarantee the removal of all malicious software. For further support on vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for baes-x →

Share this vulnerability

FAQ

The impact of this vulnerability is severe as it allows an attacker to compromise the security of the computer and exfiltrate cryptocurrency wallets, potentially leading to financial loss.

You can use the Vulert Playground (https://vulert.com/scanner) to check if your computer is affected by this vulnerability. It analyzes the package-lock.json file to identify open-source vulnerabilities in the software.

No, removing the baes-x package may not guarantee the removal of all malicious software. As the attacker may have gained full control of the compromised computer, it is important to conduct a thorough security audit to identify and remove any other potential security breaches.

If your computer is affected by this vulnerability, it is crucial to immediately rotate all secrets and keys stored on the affected computer from a different, secure computer. Remove the baes-x package and conduct a thorough security audit to identify and mitigate any potential damage caused by the malware.

To prevent future vulnerabilities, it is recommended to implement additional security measures such as using antivirus software, regularly updating all software components, and conducting regular security audits to identify and address any potential security breaches.

Related vulnerabilities

Recent vulnerabilities recorded for baes-x.

How To Fix

No fixed version is published for this vulnerability.

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