Malicious Code Injection in xenogeneic_manatee_z3n: A Threat to npm Packages

xenogeneic_manatee_z3n Updated 18 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-111112: Malicious code in xenogeneic_manatee_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 package 'xenogeneic_manatee_z3n' 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 the npm registry by flooding it with derivative packages. These packages are designed to inflate developer reputation scores through automated publishing scripts, which can lead to significant pollution of the npm registry and compromise the integrity of the ecosystem.

Vulnerability Detail

The vulnerability in 'xenogeneic_manatee_z3n' originates from its association with the tea.xyz token reward campaign. The malicious code embedded within the package modifies the package.json file by removing private flags, altering version numbers, and generating random package names. This behavior not only affects the affected package but also contributes to the overall degradation of the npm registry by continuously republishing variants, making it difficult for developers to trust the integrity of packages.

How To Fix

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

npm uninstall xenogeneic_manatee_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 'xenogeneic_manatee_z3n' package and look for alternative packages that provide similar functionality without the associated risks. Additionally, you can monitor your project for any unauthorized changes to the package.json file.

Conclusion

The 'xenogeneic_manatee_z3n' package poses a significant threat 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. Utilizing tools like Vulert can aid in maintaining the security of your applications.

See every vulnerability recorded for xenogeneic_manatee_z3n →

Share this vulnerability

FAQ

The main issue is that it contains malicious code that modifies package.json and floods the npm registry with derivative packages.

You can use Vulert to monitor your application for vulnerabilities. With Vulert, you can check your package-lock.json file to see if your application is affected without requiring any installation.

If you have installed the 'xenogeneic_manatee_z3n' package, you should uninstall it immediately using 'npm uninstall xenogeneic_manatee_z3n'.

Yes, you should look for alternative packages that provide similar functionality but do not have known vulnerabilities.

Vulert helps by monitoring your package-lock.json file for open-source vulnerabilities in real-time, alerting you to any issues without requiring access to your code or installation.

How To Fix

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

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