Malicious Code Injection in fancy_cricket_z3n: A Threat to npm Ecosystem

fancy_cricket_z3n Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-94433: Malicious code in fancy_cricket_z3n (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

fancy_cricket_z3n is an npm package that is part of a broader campaign exploiting the npm registry. It is designed to facilitate token reward mechanisms, but it has been compromised to include malicious scripts that manipulate package metadata. This vulnerability poses a significant risk to developers relying on this package for legitimate purposes.

Vulnerability Detail

The vulnerability originates from the package being part of a token reward campaign that floods the npm registry with derivative packages. It contains scripts that automatically modify the package.json file, removing private flags and changing version numbers. Additionally, it generates random package names, which leads to pollution of the npm registry. This malicious behavior can inflate developer reputation scores fraudulently and compromise the integrity of the npm ecosystem.

How To Fix

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

npm uninstall fancy_cricket_z3n

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 fancy_cricket_z3n package altogether and look for alternative packages that provide similar functionality without the associated risks.

Conclusion

The fancy_cricket_z3n package has been identified as a vector for malicious code injection, posing significant risks to developers and the npm ecosystem. Immediate action is required to remove the package and safeguard your projects. Utilizing tools like Vulert can help in monitoring and managing such vulnerabilities effectively.

See every vulnerability recorded for fancy_cricket_z3n →

Share this vulnerability

FAQ

fancy_cricket_z3n is an npm package that has been compromised to include malicious code aimed at manipulating package metadata.

The vulnerability can lead to unauthorized changes in your package.json file, potentially compromising your project's integrity and security.

You should uninstall the package immediately using 'npm uninstall fancy_cricket_z3n' and check for any dependencies that may be affected.

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

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

How To Fix

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

npm uninstall fancy_cricket_z3n

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