Malicious Code Injection in flaky_crab_z3n Package

flaky_crab_z3n Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-102809: Malicious code in flaky_crab_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

The flaky_crab_z3n package is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. It is designed to facilitate the automatic generation and publication of derivative packages. This package is primarily used by developers to manage dependencies in JavaScript applications. However, it has been compromised to include malicious scripts that can manipulate package metadata and flood the npm registry.

Vulnerability Detail

The vulnerability in flaky_crab_z3n stems from its inclusion in a malicious campaign that modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior is intended to inflate developer reputation scores for token rewards, leading to potential pollution of the npm registry and compromising the integrity of the ecosystem. The malicious payload can also lead to unintentional exposure of sensitive information if private flags are removed.

How To Fix

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

npm uninstall flaky_crab_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 prevent the installation of flaky_crab_z3n by using npm's package-lock.json to lock your dependencies. Additionally, consider using a tool like Vulert to monitor your dependencies for vulnerabilities. You can check if your application is affected by this vulnerability using the Vulert playground at https://vulert.com/scanner without any signup.

Conclusion

The flaky_crab_z3n package has been identified as part of a malicious campaign that poses significant risks to developers and the npm ecosystem. It is crucial to take immediate action to remove this package and monitor your dependencies for any vulnerabilities.

See every vulnerability recorded for flaky_crab_z3n →

Share this vulnerability

FAQ

flaky_crab_z3n is an npm package that is part of a malicious campaign aimed at inflating developer reputation scores through automated publishing of derivative packages.

The vulnerability can lead to the pollution of the npm registry, potential exposure of sensitive information, and compromise the integrity of your application's dependencies.

You should uninstall the flaky_crab_z3n package immediately and check your package-lock.json for any references to it.

Yes, you can use tools like Vulert, which monitors your package-lock.json for vulnerabilities in real-time without requiring code access or installation.

You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.

How To Fix

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

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