Malicious Code Injection in strong_bedbug_0xrequest Package

strong_bedbug_0xrequest Updated 18 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-109202: Malicious code in strong_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 Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The strong_bedbug_0xrequest package is part of the npm ecosystem, primarily used for managing JavaScript dependencies. It is often utilized in various applications for its functionalities related to network requests. However, this package has been identified as part of a malicious campaign that aims to manipulate the npm registry by creating and publishing numerous derivative packages with altered metadata.

Vulnerability Detail

The vulnerability originates from the strong_bedbug_0xrequest package being involved in a token reward campaign that floods the npm registry with malicious packages. These packages contain scripts that automatically modify the package.json file, removing private flags, changing version numbers, and generating random package names. The malicious payload can lead to reputation inflation for developers and pollution of the npm registry, posing significant risks to the integrity of the ecosystem.

How To Fix

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

npm uninstall strong_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 avoid using the strong_bedbug_0xrequest package and replace it with a trusted alternative that provides similar functionality. Additionally, ensure to audit your package dependencies regularly to identify and mitigate any potential vulnerabilities.

Conclusion

The strong_bedbug_0xrequest package poses a significant security risk due to its involvement in a malicious campaign that alters package metadata and floods the npm registry. It is crucial to remove this package from your projects and utilize tools like Vulert to monitor for vulnerabilities in your software.

See every vulnerability recorded for strong_bedbug_0xrequest →

Share this vulnerability

FAQ

It is an npm package used for managing JavaScript dependencies, but it has been identified as malicious.

The vulnerability can lead to the injection of malicious code, which may compromise your application's security and integrity.

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

Yes, Vulert allows you to monitor and alert for open-source vulnerabilities in your software using just the package-lock.json file.

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

How To Fix

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

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