Malicious Code Detected in baymax-logger: A Critical Security Alert

baymax-logger Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-15518: Malicious code in baymax-logger (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 baymax-logger package is a logging utility designed for Node.js applications, providing developers with tools to log and manage application events efficiently. However, it has been identified to contain malicious code, posing significant security risks to applications that utilize it. This vulnerability can lead to unauthorized access or data breaches, making it crucial for users to address it promptly.

Vulnerability Detail

The vulnerability in baymax-logger originates from the inclusion of malicious code within the package. This code can execute harmful actions without the user's consent, potentially compromising sensitive data or system integrity. The issue affects all versions starting from 0, and it is critical for developers to be aware of the risks associated with using this package in their projects.

How To Fix

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

npm uninstall baymax-logger

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, consider removing the baymax-logger package from your project until a secure version is released. You can do this by running: npm uninstall baymax-logger. Alternatively, you may look for other logging packages that do not have known vulnerabilities.

Conclusion

The discovery of malicious code in the baymax-logger package highlights the importance of maintaining secure coding practices and regularly updating dependencies. Users are urged to take immediate action to mitigate risks associated with this vulnerability by updating or removing the affected package.

See every vulnerability recorded for baymax-logger →

Share this vulnerability

FAQ

Baymax-logger is a logging utility for Node.js applications that helps developers manage application logs.

The malicious code can execute unauthorized actions, potentially leading to data breaches or system compromise.

You can use Vulert's playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.

If you cannot update the package, consider uninstalling it and using an alternative logging package until a secure version is available.

You can visit Vulert at https://vulert.com, which monitors and alerts for open-source vulnerabilities in real-time using just your package-lock.json.

How To Fix

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

npm uninstall baymax-logger

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