Malicious Code Injection in liberal_flea_z3n Package

liberal_flea_z3n Updated 25 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-128179: Malicious code in liberal_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 liberal_flea_z3n package is part of the npm ecosystem, primarily used for JavaScript development. It is associated with the tea.xyz token reward campaign, which has been known to flood the npm registry with various packages. This package, like others in the campaign, is designed to manipulate npm's publishing system, potentially harming developers' reputations and polluting the registry.

Vulnerability Detail

The vulnerability in the liberal_flea_z3n package stems from its malicious code that modifies the package.json file. It removes private flags, alters version numbers, and generates random package names, which are then republished to inflate developer reputation scores for token rewards. This behavior not only compromises the integrity of the npm registry but also poses risks to developers who may unknowingly depend on these malicious packages.

How To Fix

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

npm uninstall liberal_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 workaround, you can prevent the installation of this package by using npm's package-lock.json file to monitor dependencies. Ensure that your project does not include liberal_flea_z3n in its dependencies. Additionally, consider using tools like Vulert to monitor your project for vulnerabilities.

Conclusion

The liberal_flea_z3n package poses a significant risk due to its malicious code that alters package metadata and floods the npm registry. It is crucial for developers to remove this package and monitor their projects for vulnerabilities using tools like Vulert.

See every vulnerability recorded for liberal_flea_z3n →

Share this vulnerability

FAQ

liberal_flea_z3n is an npm package associated with the tea.xyz token reward campaign, known for flooding the npm registry with malicious packages.

The malicious code modifies your package.json file, potentially leading to the publication of unauthorized packages and harming your project's integrity.

You should uninstall the liberal_flea_z3n package immediately using the command: npm uninstall liberal_flea_z3n.

Yes, Vulert can monitor your package-lock.json file for vulnerabilities, including those related to the liberal_flea_z3n package, and alert you in real-time.

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 liberal_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