Malicious Code Injection in Comprehensive Whale 0xRequest Package

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-100796: Malicious code in comprehensive_whale_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 Comprehensive Whale 0xRequest package is part of the npm ecosystem, designed to facilitate various functionalities within JavaScript applications. However, it has been identified as part of a malicious campaign that floods the npm registry with derivative packages. This package, like others in the campaign, is engineered to manipulate developer reputation scores through automated publishing scripts.

Vulnerability Detail

The vulnerability originates from the package being associated with the tea.xyz token reward campaign, which employs malicious scripts to alter package.json files. These scripts remove private flags, modify version numbers, and generate random package names, leading to the continuous republishing of variants that pollute the npm registry. This can result in compromised developer environments and potential exploitation of applications relying on this package.

How To Fix

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

npm uninstall comprehensive_whale_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 Comprehensive Whale 0xRequest package and look for alternative libraries that provide similar functionality without the associated risks. Additionally, you can use tools like Vulert to monitor your package-lock.json for vulnerabilities.

Conclusion

The Comprehensive Whale 0xRequest package poses a significant risk due to its association with malicious activities aimed at manipulating npm registry data. It is crucial for developers to remove this package and monitor their applications for vulnerabilities to ensure the security and integrity of their projects.

See every vulnerability recorded for comprehensive_whale_0xrequest →

Share this vulnerability

FAQ

It is an npm package that has been identified as part of a malicious campaign aimed at manipulating developer reputation scores.

The vulnerability can lead to the injection of malicious code, compromising the integrity of your application and potentially exposing it to further attacks.

You should uninstall the package immediately and monitor your project for any other potentially vulnerable dependencies.

Yes, you can use Vulert's playground at Vulert Scanner to check if your application is affected by this vulnerability using just your package-lock.json.

Regularly audit your dependencies, keep them updated, and utilize tools like Vulert to monitor for vulnerabilities in real-time.

How To Fix

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

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