Malicious Code Injection in bad_canid_0xrequest Package

bad_canid_0xrequest Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-99738: Malicious code in bad_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 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 bad_canid_0xrequest package is part of the npm ecosystem, which is widely used for managing JavaScript packages. This package is associated with the tea.xyz token reward campaign, which has been known to flood the npm registry with malicious packages. The functionality of this package is compromised due to its involvement in generating and publishing derivative packages with altered metadata, aimed at inflating developer reputation scores.

Vulnerability Detail

The vulnerability in the bad_canid_0xrequest package stems from its malicious payload that modifies the package.json file. This payload removes private flags, alters version numbers, and generates random package names, leading to pollution of the npm registry. The origin of this vulnerability is linked to a campaign that exploits npm's publishing mechanisms, potentially allowing attackers to manipulate package integrity and developer trust. The ramifications include the risk of unintentional installation of malicious packages by developers, which can lead to further security breaches.

How To Fix

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

npm uninstall bad_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 bad_canid_0xrequest package until a secure version is released. Additionally, consider using the following command to uninstall the package: 'npm uninstall bad_canid_0xrequest'.

Conclusion

The bad_canid_0xrequest package poses a significant security risk due to its malicious code that alters package metadata and floods the npm registry. It is crucial for developers to be aware of this vulnerability, take necessary actions to update or uninstall the package, and utilize tools like Vulert for ongoing monitoring of open-source vulnerabilities.

See every vulnerability recorded for bad_canid_0xrequest →

Share this vulnerability

FAQ

The bad_canid_0xrequest package is an npm package that has been identified as malicious, involved in generating and publishing derivative packages to inflate developer reputation scores.

This vulnerability can lead to the installation of malicious code, which may compromise your application's integrity and security.

If you have installed the bad_canid_0xrequest package, it is recommended to uninstall it immediately and monitor your application for any unusual behavior.

Yes, you can use Vulert, which monitors and alerts in real-time for open-source vulnerabilities in your software using just package-lock.json. You can check if your application is affected by this vulnerability using the Vulert playground.

You can use the Vulert playground at Vulert Scanner to check if your application is affected by the bad_canid_0xrequest vulnerability without requiring any signup.

How To Fix

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

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