Malicious Code Injection in separate_cricket_0xrequest Package - npm Vulnerability
Summary
MAL-2025-108551: Malicious code in separate_cricket_0xrequest (npm). Affected versions are not published. No fix is published. How to fix ↓
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.
No signup required · Results in about 60 seconds
Background
The separate_cricket_0xrequest package is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package, like others in the campaign, is designed to inflate developer reputation scores through the automatic generation and publishing of derivative packages. It modifies package metadata and continuously republishes variants, contributing to npm registry pollution.
Vulnerability Detail
The vulnerability originates from the malicious intent behind the separate_cricket_0xrequest package. It contains scripts that alter the package.json file by removing private flags, changing version numbers, and generating random package names. This behavior not only compromises the integrity of the npm registry but also poses risks to developers who may unknowingly use these compromised packages, leading to potential security breaches and loss of trust in the ecosystem.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall separate_cricket_0xrequestIf 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 separate_cricket_0xrequest package and look for alternative packages that provide similar functionality without the associated risks. Additionally, you can monitor your dependencies using tools like Vulert to receive alerts for any vulnerabilities.
Conclusion
The separate_cricket_0xrequest package poses significant risks due to its malicious code designed to manipulate package metadata and pollute the npm registry. It is crucial for developers to remove this package and monitor their dependencies for vulnerabilities to maintain the integrity of their projects.
See every vulnerability recorded for separate_cricket_0xrequest →
FAQ
It is an npm package involved in the tea.xyz token reward campaign, which aims to inflate developer reputation scores through malicious practices.
Using this package can compromise your project's integrity, lead to security breaches, and contribute to the pollution of the npm registry.
You should uninstall the package immediately using 'npm uninstall separate_cricket_0xrequest' and check for any references in your package-lock.json.
Yes, you can use Vulert to monitor your project for open-source vulnerabilities in real-time without needing to access the code or installation.
You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.
