Malicious Code Injection in bad_mite_0xrequest Package

bad_mite_0xrequest Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-99741: Malicious code in bad_mite_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 MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

The bad_mite_0xrequest package is part of the npm ecosystem, primarily used for various JavaScript applications. It has gained notoriety due to its involvement in a token reward campaign that has led to the proliferation of malicious packages. This package is designed to inflate developer reputation scores through automated publishing scripts, which can compromise the integrity of the npm registry.

Vulnerability Detail

The vulnerability in the bad_mite_0xrequest package stems from its malicious code that modifies the package.json file. This code removes private flags, alters version numbers, and generates random package names, leading to the continuous republishing of variants. The origin of this issue is linked to the tea.xyz token reward campaign, which aims to manipulate npm's reputation system. The ramifications include potential pollution of the npm registry, making it difficult for developers to find legitimate packages and increasing the risk of dependency confusion attacks.

How To Fix

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

npm uninstall bad_mite_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, avoid using the bad_mite_0xrequest package and consider using alternative packages that provide similar functionality without the associated risks.

Conclusion

The bad_mite_0xrequest package poses a significant risk due to its malicious code that alters package metadata and floods the npm registry. It is crucial to remove this package and monitor your dependencies for vulnerabilities to maintain the integrity of your applications.

See every vulnerability recorded for bad_mite_0xrequest →

Share this vulnerability

FAQ

The bad_mite_0xrequest package is an npm package involved in a malicious campaign to inflate developer reputation scores through automated publishing.

The vulnerability can lead to the pollution of the npm registry, making it harder to find legitimate packages and increasing security risks.

You should uninstall the bad_mite_0xrequest package immediately and monitor your application for any unusual behavior.

Yes, you can use Vulert, which monitors and alerts for open-source vulnerabilities in your software using just package-lock.json.

Yes, you can use the Vulert playground at Vulert Scanner to check for vulnerabilities in your application without any signup.

How To Fix

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

npm uninstall bad_mite_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