Malicious Code Vulnerability in upset_trout_0xrequest Package

upset_trout_0xrequest Updated 18 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-110219: Malicious code in upset_trout_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 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 upset_trout_0xrequest 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 linked to the proliferation of malicious packages designed to inflate developer reputation scores. The functionality of this package is compromised due to its involvement in autopublishing scripts that generate and publish derivative packages with random names, ultimately polluting the npm registry.

Vulnerability Detail

The vulnerability stems from the malicious code embedded in the upset_trout_0xrequest package. It modifies the package.json file to remove private flags, alters version numbers, and generates random package names, which can lead to significant security risks. The malicious payload continuously republishes these variants, making it difficult for developers to maintain the integrity of their projects. This behavior can result in unauthorized access to sensitive data and a compromised development environment.

How To Fix

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

npm uninstall upset_trout_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 upset_trout_0xrequest package and look for alternative packages that provide similar functionality without the associated risks. Additionally, you can monitor your package dependencies using tools like Vulert, which alerts you to open-source vulnerabilities in real-time.

Conclusion

The upset_trout_0xrequest package contains malicious code that poses a significant risk to developers and their projects. It is crucial to remove this package and monitor your dependencies for vulnerabilities. Utilizing tools like Vulert can help maintain the security of your software.

See every vulnerability recorded for upset_trout_0xrequest →

Share this vulnerability

FAQ

It is an npm package associated with the tea.xyz token reward campaign, known for containing malicious code.

The vulnerability can lead to unauthorized modifications of your package.json file and the introduction of malicious packages into your project.

You should uninstall the upset_trout_0xrequest package immediately and monitor your project for any unusual behavior.

Yes, you can use Vulert, which monitors your package-lock.json for vulnerabilities in real-time without requiring code access.

You can use the Vulert playground at Vulert Scanner to check for vulnerabilities in your application without signing up.

How To Fix

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

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