Malicious Code Injection in similar_bug_0xrequest Package

similar_bug_0xrequest Updated 18 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-108693: Malicious code in similar_bug_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 similar_bug_0xrequest package is part of a series of npm packages that emerged during the tea.xyz token reward campaign. These packages are designed to automate the generation and publication of derivative packages, often with randomized names, to inflate developer reputation scores for token rewards. The package's functionality is compromised by malicious scripts that alter its metadata and behavior.

Vulnerability Detail

This vulnerability originates from the malicious code embedded within the similar_bug_0xrequest package. It modifies the package.json file to remove private flags, alters version numbers, and generates random package names. The scripts continuously republish these variants, leading to pollution of the npm registry and potential security risks for developers who unknowingly install these compromised packages. The ramifications include loss of control over package integrity and potential exploitation of systems using these packages.

How To Fix

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

npm uninstall similar_bug_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 similar_bug_0xrequest package and consider alternative packages that provide similar functionality without the associated risks. Additionally, you can use the following command to uninstall the package: npm uninstall similar_bug_0xrequest.

Conclusion

The similar_bug_0xrequest package poses a significant security risk due to its embedded malicious code that alters package metadata and repackages it for distribution. It is essential to remove this package from your projects and monitor for similar vulnerabilities using tools like Vulert.

See every vulnerability recorded for similar_bug_0xrequest →

Share this vulnerability

FAQ

The similar_bug_0xrequest package is an npm package that is part of a malicious campaign aimed at inflating developer reputation scores through automated publishing of compromised packages.

The vulnerability can lead to the installation of malicious code that modifies your project's package metadata, potentially compromising its integrity and security.

If you have installed the similar_bug_0xrequest package, you should uninstall it immediately and check for any other compromised packages in your project.

You can use tools like Vulert, which monitors your package-lock.json file to alert you in real-time for open-source vulnerabilities. You can also check your application using the Vulert playground without any signup.

Yes, consider using other reputable packages that offer similar functionality without the associated risks of malicious code.

How To Fix

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

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