Malicious Code Vulnerability in ready_harrier_0xrequest Package

ready_harrier_0xrequest Updated 18 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-107756: Malicious code in ready_harrier_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 ready_harrier_0xrequest package is part of a broader ecosystem of npm packages that have been associated with the tea.xyz token reward campaign. These packages are designed to automate the generation and publication of derivative packages, often with randomized names. This functionality is exploited to inflate developer reputation scores for token rewards, making the package susceptible to malicious activities.

Vulnerability Detail

The vulnerability originates from the package's malicious payload, which modifies the package.json file to remove private flags and alters version numbers. It generates random Indonesian-themed package names and continuously republishes variants, leading to pollution of the npm registry. This behavior can compromise the integrity of the npm ecosystem and potentially expose users to further security risks.

How To Fix

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

npm uninstall ready_harrier_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, consider using the following command to uninstall the vulnerable package: npm uninstall ready_harrier_0xrequest. This will help mitigate the risks associated with the malicious code until a proper fix is implemented.

Conclusion

The ready_harrier_0xrequest package contains a serious vulnerability that can compromise the integrity of your project and the npm ecosystem. It is crucial to remove this package and monitor for any updates or patches. Utilizing tools like Vulert can help keep your project secure from such vulnerabilities.

See every vulnerability recorded for ready_harrier_0xrequest →

Share this vulnerability

FAQ

It is an npm package associated with the tea.xyz token reward campaign, designed to automate the publication of derivative packages.

The vulnerability can lead to the modification of your package.json file and the pollution of the npm registry, potentially exposing your project to further security risks.

Currently, there is no patch available. It is advisable to remove the package until a safe version is released.

You can use Vulert, which monitors and alerts in real-time for open-source vulnerabilities using just your package-lock.json file.

You can use the Vulert playground at Vulert Scanner to check if your application is affected without requiring any signup.

How To Fix

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

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