Malicious Code Injection in mighty_bedbug_0xrequest Package

mighty_bedbug_0xrequest Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-105829: Malicious code in mighty_bedbug_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 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 mighty_bedbug_0xrequest package is part of the npm ecosystem, which is widely used for JavaScript package management. This package is associated with the tea.xyz token reward campaign, which has been known to flood the npm registry with malicious packages. The primary function of this package is to facilitate the automatic generation and publication of derivative packages, which can inflate developer reputation scores for token rewards. However, it has been compromised, leading to significant security concerns.

Vulnerability Detail

The vulnerability originates from the package's design to include autopublish scripts that modify the package.json file. These modifications remove private flags, change version numbers, and generate random package names, which can lead to pollution of the npm registry. The malicious payload can potentially allow unauthorized access to sensitive information and compromise the integrity of the software supply chain, making it a critical security issue.

How To Fix

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

npm uninstall mighty_bedbug_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 prevent the package from being used in your project by adding it to your project's .npmrc file with the following line: 'package-lock=false'. This will stop npm from installing the package until it is removed or updated.

Conclusion

The mighty_bedbug_0xrequest package has been identified as containing malicious code that can compromise the integrity of your software projects. It is essential to remove this package and monitor your applications for any vulnerabilities. Utilizing tools like Vulert can help you stay informed about potential threats.

See every vulnerability recorded for mighty_bedbug_0xrequest →

Share this vulnerability

FAQ

The vulnerability can lead to unauthorized modifications of your package.json file, potentially exposing sensitive information and compromising your project's integrity.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. By simply uploading your package-lock.json file, you can check for vulnerabilities without needing to install any software.

Yes, you can temporarily prevent the package from being installed by modifying your .npmrc file to disable package-lock.

It is crucial to uninstall the package immediately and monitor your project for any unusual behavior or vulnerabilities.

You can find detailed information in the vulnerability report on the official GitHub repository for malicious packages.

How To Fix

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

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