Malicious Code Vulnerability in liberal_eagle_z3n: Exploitation of npm Registry

liberal_eagle_z3n Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-98789: Malicious code in liberal_eagle_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 package liberal_eagle_z3n is part of a broader set of malicious packages that emerged during the tea.xyz token reward campaign. These packages are designed to inflate developer reputation scores by automatically generating and publishing derivative packages with randomized names. This behavior not only clutters the npm registry but also poses security risks to developers who may unknowingly integrate these packages into their projects.

Vulnerability Detail

The vulnerability in liberal_eagle_z3n stems from its malicious payload, which modifies the package.json file by removing private flags, altering version numbers, and generating random package names. This behavior leads to the continuous republishing of variants, effectively polluting the npm registry. The origin of this vulnerability is linked to the tea.xyz token reward campaign, which incentivizes the creation of such packages to manipulate developer reputation scores. The ramifications include potential security risks for developers and users who may inadvertently use these compromised packages, leading to further exploitation.

How To Fix

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

npm uninstall liberal_eagle_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 liberal_eagle_z3n package and replace it with a similar, trusted package that provides the same functionality without the associated risks.

Conclusion

The liberal_eagle_z3n package presents a significant security risk due to its malicious behavior aimed at manipulating npm registry reputation scores. Developers are advised to remove this package from their projects and utilize trusted alternatives. Regular monitoring for vulnerabilities is crucial to maintaining application security.

See every vulnerability recorded for liberal_eagle_z3n →

Share this vulnerability

FAQ

liberal_eagle_z3n is an npm package that has been identified as malicious, designed to inflate developer reputation scores through automated publishing of derivative packages.

The vulnerability can lead to the inclusion of malicious code in your project, potentially compromising security and functionality.

You should uninstall the liberal_eagle_z3n package immediately and replace it with a trusted alternative.

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

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