Malicious Code Injection in then_manatee_0xrequest Package

then_manatee_0xrequest Updated 18 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-109582: Malicious code in then_manatee_0xrequest (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 Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The then_manatee_0xrequest package is part of the npm ecosystem, often used in JavaScript applications. 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 affecting developers' reputations and the integrity of the npm registry.

Vulnerability Detail

This vulnerability originates from the malicious design of the then_manatee_0xrequest package, which contains scripts that automatically generate and publish derivative packages with randomized names. These scripts modify the package.json file to remove private flags, alter version numbers, and continuously republish variants to pollute the npm registry. The ramifications include compromised developer reputations, potential security risks for applications using these packages, and a cluttered npm registry that makes it difficult to find legitimate packages.

How To Fix

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

npm uninstall then_manatee_0xrequest

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

Currently, the best workaround is to avoid using the then_manatee_0xrequest package altogether. If it is already in use, ensure that you remove it and monitor your dependencies for any similar malicious packages. You can use tools like Vulert to monitor your project for vulnerabilities in real-time.

Conclusion

The then_manatee_0xrequest package poses a significant risk due to its malicious design aimed at manipulating the npm registry. It is essential to remove this package and monitor your dependencies to ensure the security and integrity of your applications.

See every vulnerability recorded for then_manatee_0xrequest →

Share this vulnerability

FAQ

It is an npm package associated with the tea.xyz token reward campaign, designed to manipulate the npm publishing system.

The vulnerability can lead to the pollution of the npm registry and compromise the integrity of your application by introducing malicious code.

You should uninstall the then_manatee_0xrequest package immediately and check your project for any other potentially malicious packages.

Yes, you can use Vulert to monitor your project for open-source vulnerabilities in real-time without needing to access the code or installation.

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 then_manatee_0xrequest

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