Malicious Code Injection in appalling_crayfish_z3n Package

appalling_crayfish_z3n Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-93247: Malicious code in appalling_crayfish_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 Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

Background

The appalling_crayfish_z3n package is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to generate and publish derivative packages with randomized names, aiming to inflate developer reputation scores for token rewards. However, it has been identified as containing malicious scripts that compromise its integrity and the security of applications that depend on it.

Vulnerability Detail

The vulnerability in the appalling_crayfish_z3n package stems from its inclusion in a malicious campaign that utilizes autopublish scripts to modify package.json files. These scripts remove private flags, alter version numbers, and generate random package names, leading to the continuous republishing of variants that pollute the npm registry. This can result in compromised applications, as developers may unknowingly install these malicious packages, exposing their systems to potential security threats.

How To Fix

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

npm uninstall appalling_crayfish_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 appalling_crayfish_z3n package altogether. If it is a dependency of another package, consider using alternative packages that do not have known vulnerabilities. Additionally, you can monitor your project for vulnerabilities using tools like Vulert, which can alert you in real-time for open-source vulnerabilities without requiring code access or installation.

Conclusion

The appalling_crayfish_z3n package poses a significant security risk due to its malicious code that modifies package.json files and repopulates the npm registry with harmful variants. It is crucial for developers to remove this package and monitor their projects for vulnerabilities to maintain application security.

See every vulnerability recorded for appalling_crayfish_z3n →

Share this vulnerability

FAQ

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

The vulnerability can lead to the installation of malicious packages that compromise your application's security, potentially exposing sensitive data or allowing unauthorized access.

You should uninstall the appalling_crayfish_z3n package immediately and check for any other dependencies that may be affected. Consider using alternative packages.

You can use Vulert to monitor your project for open-source vulnerabilities in real-time. It requires only your package-lock.json file to provide alerts.

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

Sponsored Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

How To Fix

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

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