Malicious Code Injection in itchy_booby_0xrequest Package

itchy_booby_0xrequest Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-104438: Malicious code in itchy_booby_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 itchy_booby_0xrequest package is part of the npm ecosystem, often utilized for various JavaScript functionalities. However, it has been identified as part of a malicious campaign associated with the tea.xyz token reward system. This package is designed to inflate developer reputation scores by automatically generating and publishing derivative packages with randomized names, which can lead to significant pollution of the npm registry.

Vulnerability Detail

The vulnerability originates from the package's malicious payload, which modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior not only compromises the integrity of the npm registry but also poses risks to developers who may unknowingly install these malicious packages, potentially leading to security breaches and loss of trust in the npm ecosystem.

How To Fix

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

npm uninstall itchy_booby_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 workaround, you can avoid using the itchy_booby_0xrequest package altogether and look for alternative packages that provide similar functionality without the associated risks. Additionally, regularly audit your dependencies using tools like npm audit to identify and address vulnerabilities.

Conclusion

The itchy_booby_0xrequest package poses a significant risk due to its malicious code designed to manipulate the npm registry. It is crucial for developers to be vigilant about the packages they use and to take immediate action if they find this package in their projects. Regular audits and monitoring can help maintain the integrity of your software.

See every vulnerability recorded for itchy_booby_0xrequest →

Share this vulnerability

FAQ

It is an npm package that has been identified as part of a malicious campaign to inflate developer reputation scores through the automatic generation of derivative packages.

If you have this package installed, it can compromise your project's integrity by modifying your package.json file and potentially introducing other malicious packages into your environment.

You should uninstall the package immediately and check for any dependencies that may rely on it. Consider using alternative packages.

You can use tools like npm audit to scan your project for vulnerabilities. Additionally, Vulert can monitor your package-lock.json for real-time alerts on open-source vulnerabilities.

Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring any signup.

How To Fix

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

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