Malicious Code Vulnerability in xenogeneic_otter_0xrequest Package

xenogeneic_otter_0xrequest Updated 18 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-111114: Malicious code in xenogeneic_otter_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 Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The xenogeneic_otter_0xrequest package 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 inflate developer reputation scores through the automatic generation and publication of derivative packages. The presence of this package in a project can lead to significant security risks and pollution of the npm registry.

Vulnerability Detail

The vulnerability originates from the package being associated with the tea.xyz token reward campaign, which floods npm with malicious packages. These packages contain scripts designed to modify the package.json file by removing private flags, changing version numbers, and generating random package names. This behavior not only compromises the integrity of the affected projects but also contributes to the pollution of the npm registry, making it difficult for developers to find legitimate packages.

How To Fix

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

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

As a temporary workaround, you can avoid using the xenogeneic_otter_0xrequest package and instead look for alternative packages that provide similar functionality without the associated risks. Always verify the source and reputation of packages before including them in your project.

Conclusion

The xenogeneic_otter_0xrequest package poses a significant security risk due to its association with a malicious campaign. It is crucial for developers to be vigilant, regularly check their dependencies, and utilize tools like Vulert to monitor for vulnerabilities. Removing this package and ensuring the integrity of your project is essential for maintaining security.

See every vulnerability recorded for xenogeneic_otter_0xrequest →

Share this vulnerability

FAQ

It is an npm package that has been identified as part of a malicious campaign to inflate developer reputation scores through the automatic generation of derivative packages.

The vulnerability can lead to the modification of your package.json file, potentially exposing your project to further security risks and polluting the npm registry.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software. By using the Vulert playground, you can check if your application is affected without any signup.

You should uninstall the xenogeneic_otter_0xrequest package immediately and review your other dependencies for any potential vulnerabilities.

There is no patch for the xenogeneic_otter_0xrequest package itself, as it is recommended to remove it entirely from your project.

How To Fix

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

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