Malicious Code Injection in upset_canid_0xrequest Package

upset_canid_0xrequest Updated 18 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-110213: Malicious code in upset_canid_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 upset_canid_0xrequest package is part of a series of npm packages associated with the tea.xyz token reward campaign. These packages are designed to automate the generation and publication of derivative packages, often with randomized names, to inflate developer reputation scores for token rewards. This behavior raises significant concerns regarding the integrity and reliability of the npm ecosystem.

Vulnerability Detail

The vulnerability in the upset_canid_0xrequest package stems from its malicious payload, which modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior not only compromises the integrity of the affected package but also leads to pollution of the npm registry, making it difficult for developers to find legitimate packages. The origin of this vulnerability is linked to the broader trend of malicious packages flooding the npm ecosystem, specifically targeting developers seeking rewards through token campaigns.

How To Fix

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

npm uninstall upset_canid_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_canid_0xrequest package and replace it with a trusted alternative that provides similar functionality. Always verify the integrity and source of any package before including it in your project.

Conclusion

The upset_canid_0xrequest package poses a significant risk due to its malicious code that alters package metadata and pollutes the npm registry. It is crucial for developers to be vigilant and remove such packages from their projects, ensuring the use of secure alternatives and monitoring tools like Vulert to maintain the integrity of their applications.

See every vulnerability recorded for upset_canid_0xrequest →

Share this vulnerability

FAQ

The upset_canid_0xrequest package is part of a series of npm packages that are involved in automating the generation of derivative packages for token rewards.

This vulnerability can compromise the integrity of your project by introducing malicious code that modifies your package.json and pollutes the npm registry.

You should uninstall the upset_canid_0xrequest package immediately and replace it with a trusted alternative.

You can use tools like Vulert, which monitors your package-lock.json file to alert you in real-time for open-source vulnerabilities.

Yes, 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 upset_canid_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