Malicious Code Injection in official_manatee_z3n Package

official_manatee_z3n Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-95737: Malicious code in official_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 official_manatee_z3n package is part of the npm ecosystem, which is widely used for JavaScript package management. This package is associated with the tea.xyz token reward campaign, which has been known to flood the npm registry with malicious packages. The primary functionality of this package is to serve as a token reward mechanism, but it has been compromised to include harmful scripts that can affect developers and their projects.

Vulnerability Detail

The vulnerability in the official_manatee_z3n package stems from malicious code that modifies the package.json file to remove private flags and alters version numbers. It generates random package names, often themed around Indonesian culture, and continuously republishes these variants to pollute the npm registry. This behavior can inflate developer reputation scores fraudulently and lead to the distribution of compromised packages across the ecosystem, potentially affecting numerous projects that rely on npm.

How To Fix

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

npm uninstall official_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 remove the official_manatee_z3n package from your project by executing: npm uninstall official_manatee_z3n. This will prevent any malicious code from executing until a safe version is available.

Conclusion

The official_manatee_z3n package has been identified as containing malicious code that can compromise projects using it. It is crucial to take immediate action by updating or removing the package to safeguard your development environment. Utilizing tools like Vulert can help in monitoring and managing vulnerabilities effectively.

See every vulnerability recorded for official_manatee_z3n →

Share this vulnerability

FAQ

The official_manatee_z3n package is an npm package associated with the tea.xyz token reward campaign, which has been compromised to include malicious scripts.

The malicious code modifies your package.json file, removes private flags, and can lead to the publication of compromised packages, affecting the integrity of your project.

You should uninstall the official_manatee_z3n package immediately and check for any unauthorized changes in your project files.

Yes, you can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time using just your package-lock.json file. You can check your application for vulnerabilities without signing up at the Vulert playground.

Regularly update your packages, monitor for vulnerabilities using tools like Vulert, and review the packages you include in your projects for any known issues.

How To Fix

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

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