Malicious Code Injection in selected_flea_z3n Package

selected_flea_z3n Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-90457: Malicious code in selected_flea_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 Devnack Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

The selected_flea_z3n package is part of the npm ecosystem, which is widely used for JavaScript package management. This package has been identified as part of a malicious campaign that aims to exploit npm's publishing system. It is designed to automatically generate and publish derivative packages with randomized names, potentially compromising the integrity of the npm registry and affecting developers' reputations.

Vulnerability Detail

The vulnerability stems from the presence of malicious code within the selected_flea_z3n package. This code modifies the package.json file to remove private flags, alters version numbers, and generates random package names. The intent is to flood the npm registry with these variants, thereby inflating developer reputation scores for the tea protocol token rewards. This not only pollutes the npm registry but also poses a risk to developers who may unknowingly use these compromised packages.

How To Fix

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

npm uninstall selected_flea_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 measure, you can avoid using the selected_flea_z3n package and look for alternative packages that provide similar functionality without the associated risks. Additionally, regularly audit your package dependencies using tools like Vulert to monitor for vulnerabilities.

Conclusion

The selected_flea_z3n package contains malicious code that poses a significant risk to developers using npm. It is crucial to remove this package from your projects and monitor for any similar vulnerabilities using tools like Vulert. Staying informed and proactive can help safeguard your applications from potential threats.

See every vulnerability recorded for selected_flea_z3n →

Share this vulnerability

FAQ

The selected_flea_z3n package is an npm package that has been identified as part of a malicious campaign to exploit npm's publishing system.

This vulnerability can lead to the introduction of malicious code into your project, potentially compromising its security and integrity.

You should uninstall the selected_flea_z3n package immediately and check your project for any dependencies that may be affected.

You can use tools like Vulert, which monitors your package-lock.json file for vulnerabilities in real-time without requiring code access.

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

How To Fix

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

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