Malicious Code Injection in adverse_cricket_0xrequest Package

adverse_cricket_0xrequest Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-99209: Malicious code in adverse_cricket_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 MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

The adverse_cricket_0xrequest package is part of the npm ecosystem, primarily 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 numerous packages. This package, like others in the campaign, is designed to manipulate developer reputation scores through the automatic generation and publication of derivative packages.

Vulnerability Detail

The vulnerability in the adverse_cricket_0xrequest package stems from its malicious code that modifies the package.json file. This code removes private flags, alters version numbers, and generates random package names, which leads to the continuous republishing of variants. The origin of this vulnerability is linked to the tea.xyz token reward campaign, which aims to inflate developer reputation scores by polluting the npm registry with these malicious packages. The ramifications include potential security risks for applications relying on this package, as well as the degradation of the npm ecosystem's integrity.

How To Fix

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

npm uninstall adverse_cricket_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 adverse_cricket_0xrequest package and look for alternative packages that provide similar functionality without the associated risks. Always validate the source and reputation of any package before integrating it into your project.

Conclusion

The adverse_cricket_0xrequest package contains malicious code that poses significant risks to applications using it. It is crucial to remove this package and monitor your dependencies for vulnerabilities. Utilizing tools like Vulert can help you stay informed about potential security issues in your open-source projects.

See every vulnerability recorded for adverse_cricket_0xrequest →

Share this vulnerability

FAQ

It is an npm package associated with the tea.xyz token reward campaign, known for manipulating developer reputation scores.

The vulnerability can lead to security risks, including the potential exposure of sensitive information and the degradation of the npm ecosystem.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Check your application using the Vulert playground at Vulert Scanner.

There is no patch for the adverse_cricket_0xrequest package. The recommended action is to uninstall it and replace it with a secure alternative.

Uninstall the package immediately and review your project for any potential security implications. Consider using trusted alternatives.

How To Fix

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

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