Critical Malicious Code Vulnerability in @baipiaodajun/mcbots Package

@baipiaodajun/mcbots Updated 01 Sep 2026

Summary

31/08/2026
CRITICAL
No i
Critical
Not published

MAL-2026-15640: Malicious code in @baipiaodajun/mcbots (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 @baipiaodajun/mcbots package is an npm library designed for creating automated bots. It is utilized in various applications for tasks such as data scraping, automation, and interaction with web services. However, this package has been identified as containing malicious code, posing significant security risks to any system that installs it.

Vulnerability Detail

The vulnerability originates from the presence of embedded malicious code within the @baipiaodajun/mcbots package. This code can compromise the entire system where the package is installed, allowing unauthorized access to sensitive information such as secrets and keys. The malicious nature of this code means that any computer running this package should be considered fully compromised, with potential ramifications including data theft and unauthorized control over the system.

How To Fix

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

npm uninstall @baipiaodajun/mcbots

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 and securing the system. Users should ensure that they do not run any applications relying on this package until it has been completely removed.

Conclusion

The @baipiaodajun/mcbots package contains malicious code that poses a serious security threat. Immediate action is required to remove the package and secure any sensitive information. Users are encouraged to utilize tools like Vulert to monitor for vulnerabilities in their applications.

See every vulnerability recorded for @baipiaodajun/mcbots →

Share this vulnerability

FAQ

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

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check your application without needing to sign up.

No, there is currently no patched version of the @baipiaodajun/mcbots package available.

Failing to remove the package can lead to unauthorized access to your system, data theft, and potential control by malicious actors.

Yes, but ensure that you regularly monitor your dependencies for vulnerabilities and only install packages from trusted sources.

How To Fix

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

npm uninstall @baipiaodajun/mcbots

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