Malicious Code Injection in strange_cricket_z3n: A Threat to npm Ecosystem
Summary
MAL-2025-96796: Malicious code in strange_cricket_z3n (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
strange_cricket_z3n is an npm package that has been identified as part of a malicious campaign targeting the npm registry. This package is associated with the tea.xyz token reward initiative, which aims to inflate developer reputation scores through the automatic generation and publication of derivative packages. The malicious nature of this package lies in its ability to modify package metadata and republish variants, thereby polluting the npm ecosystem.
Vulnerability Detail
The vulnerability in strange_cricket_z3n stems from its inclusion in a series of malicious packages that contain scripts designed to autopublish derivative versions with altered metadata. These scripts remove private flags from package.json, change version numbers, and generate random package names, which can lead to a significant increase in the number of malicious packages in the npm registry. This not only compromises the integrity of the registry but also poses risks to developers who may unknowingly install these malicious packages, potentially leading to security breaches in their applications.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall strange_cricket_z3nIf 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 measure, you can avoid using the strange_cricket_z3n package and any other packages associated with the tea.xyz token reward campaign. Regularly audit your package dependencies using tools like npm audit to identify and mitigate potential vulnerabilities.
Conclusion
The strange_cricket_z3n package poses a significant threat to the npm ecosystem due to its malicious code designed to manipulate package metadata and republish variants. It is crucial for developers to remain vigilant, regularly audit their dependencies, and utilize tools like Vulert to monitor for vulnerabilities in real-time.
See every vulnerability recorded for strange_cricket_z3n →
FAQ
strange_cricket_z3n is an npm package that has been identified as part of a malicious campaign aimed at inflating developer reputation scores through the automatic generation of derivative packages.
The vulnerability can lead to the installation of malicious packages that may compromise your application's security, potentially allowing unauthorized access or data breaches.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. You can check your application for vulnerabilities by visiting the Vulert playground at Vulert Scanner without needing to sign up.
If you have installed strange_cricket_z3n, you should immediately uninstall it using the command npm uninstall strange_cricket_z3n and audit your project for other potential vulnerabilities.
Yes, tools like npm audit and Vulert can help you identify and manage vulnerabilities in your npm packages effectively.
