Malicious Code Injection in ordinary_leech_0xrequest Package

ordinary_leech_0xrequest Updated 18 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-106773: Malicious code in ordinary_leech_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 ordinary_leech_0xrequest package is part of the npm ecosystem, often used for various JavaScript applications. It is associated with the tea.xyz token reward campaign, which has been known to flood the npm registry with packages that contain malicious scripts. This package, like others in the campaign, is designed to manipulate developer reputation scores by generating and publishing derivative packages with randomized names.

Vulnerability Detail

The vulnerability in the ordinary_leech_0xrequest package stems from its inclusion in a malicious campaign that modifies the package.json file to remove private flags, alters version numbers, and creates random package names. This behavior leads to the continuous republishing of variants, polluting the npm registry and potentially compromising the integrity of applications that depend on this package. The malicious payload can affect developers' reputations and the overall security of the npm ecosystem.

How To Fix

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

npm uninstall ordinary_leech_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 temporarily avoid using the ordinary_leech_0xrequest package and replace it with an alternative package that provides similar functionality without the associated risks. Always ensure to review the package's reputation and security history before integrating it into your project.

Conclusion

The ordinary_leech_0xrequest package poses a significant risk due to its malicious behavior aimed at manipulating npm registry integrity. It is crucial for developers to remove this package and monitor their projects for vulnerabilities to maintain security.

See every vulnerability recorded for ordinary_leech_0xrequest →

Share this vulnerability

FAQ

ordinary_leech_0xrequest is an npm package that is part of a malicious campaign aimed at inflating developer reputation scores through the creation of derivative packages.

This vulnerability can compromise the integrity of your application by introducing malicious code that alters package configurations and potentially leads to security breaches.

You should uninstall the ordinary_leech_0xrequest package immediately and consider using alternative packages that do not have known vulnerabilities.

You can use tools like Vulert, which monitors your package-lock.json file to alert you in real-time about open-source vulnerabilities in your software.

Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.

How To Fix

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

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