Malicious Code Injection in middle_bee_0xrequest Package

middle_bee_0xrequest Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-105822: Malicious code in middle_bee_0xrequest (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 Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

Background

The middle_bee_0xrequest package is part of the npm ecosystem, often utilized in JavaScript applications for various functionalities. However, it has been identified as part of a malicious campaign that aims to inflate developer reputation scores through the tea.xyz token reward system. This package, like others in the campaign, is designed to automatically generate and publish derivative packages, which can lead to significant pollution of the npm registry.

Vulnerability Detail

The vulnerability in the middle_bee_0xrequest package stems from its association with a malicious campaign that modifies the package.json file to remove private flags and changes version numbers. It generates random package names, often themed around Indonesian culture, and continuously republishes these variants. This behavior not only compromises the integrity of the npm registry but also poses risks to developers who may unknowingly use these tainted packages, leading to potential security breaches in their applications.

How To Fix

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

npm uninstall middle_bee_0xrequest

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 middle_bee_0xrequest package from your project if it is not essential. Use the following command to uninstall it: npm uninstall middle_bee_0xrequest. Additionally, consider using alternative packages that provide similar functionality without the associated risks.

Conclusion

The middle_bee_0xrequest package poses a significant security risk due to its malicious behavior of modifying package metadata and republishing compromised versions. It is crucial for developers to take immediate action by updating or removing this package and to utilize tools like Vulert for ongoing monitoring of vulnerabilities in their applications.

See every vulnerability recorded for middle_bee_0xrequest →

Share this vulnerability

FAQ

middle_bee_0xrequest is an npm package that has been identified as part of a malicious campaign aimed at inflating developer reputation scores.

Using the compromised middle_bee_0xrequest package can lead to security breaches, as it modifies your package.json and can introduce malicious code into your application.

You should immediately update or uninstall the middle_bee_0xrequest package and review your application for any potential security issues.

Yes, you can use tools like Vulert, which monitors your package-lock.json for open-source vulnerabilities in real-time without requiring code access or installation.

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

Sponsored Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

How To Fix

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

npm uninstall middle_bee_0xrequest

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