Malicious Code Injection in burning_cougar_0xrequest Package

burning_cougar_0xrequest Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-100192: Malicious code in burning_cougar_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 Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

The burning_cougar_0xrequest package is part of the npm ecosystem, often utilized in JavaScript applications. It is associated with the tea.xyz token reward campaign, which has been known to flood npm with malicious packages. This package, like others in the campaign, is designed to manipulate npm's registry by generating and publishing derivative packages with randomized names, thereby inflating developer reputation scores.

Vulnerability Detail

The vulnerability arises from malicious code embedded within the burning_cougar_0xrequest package. This code modifies the package.json file to remove private flags, alters version numbers, and generates random package names, which leads to the continuous republishing of these variants. The origin of this vulnerability is linked to the tea.xyz token reward campaign, which aims to exploit npm's registry for fraudulent purposes. The ramifications include potential pollution of the npm registry and risks to developers who may unknowingly use these compromised packages.

How To Fix

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

npm uninstall burning_cougar_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 burning_cougar_0xrequest package altogether. If it is already in use, ensure to monitor your package-lock.json file for any unauthorized changes and remove the package immediately.

Conclusion

The burning_cougar_0xrequest package poses a significant risk due to its malicious code that alters package metadata and floods the npm registry. It is crucial for developers to be vigilant and remove such packages from their projects to maintain the integrity of their applications.

See every vulnerability recorded for burning_cougar_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 in your package.json file and may result in your application using compromised packages.

You can use the Vulert platform to monitor your package-lock.json for vulnerabilities. Visit Vulert Scanner to check your application without needing to sign up.

You should uninstall the burning_cougar_0xrequest package immediately and check for any dependencies that may be affected.

Regularly monitor your dependencies using tools like Vulert, which alerts you in real-time for open-source vulnerabilities.

How To Fix

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

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