Malicious Code Vulnerability in identical_whippet_0xrequest Package

identical_whippet_0xrequest Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-103936: Malicious code in identical_whippet_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 'identical_whippet_0xrequest' package is part of a series of npm packages that have been associated with the tea.xyz token reward campaign. These packages are designed to automate the generation and publication of derivative packages with randomized names, which can inflate developer reputation scores in exchange for token rewards. This behavior raises significant concerns regarding the integrity of the npm registry and the potential for malicious exploitation.

Vulnerability Detail

The vulnerability stems from the presence of malicious code within the 'identical_whippet_0xrequest' package. This code modifies the package.json file to remove private flags, alters version numbers, and generates random package names, thereby republishing variants to pollute the npm registry. The origin of this malicious behavior is linked to a campaign that aims to exploit npm's publishing mechanisms for fraudulent gain, potentially leading to security risks for developers and users who inadvertently install these compromised packages.

How To Fix

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

npm uninstall identical_whippet_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 'identical_whippet_0xrequest' package altogether. If you must use it, consider using a package manager that allows you to lock dependencies to specific versions, thereby preventing the installation of potentially compromised versions.

Conclusion

The 'identical_whippet_0xrequest' package contains malicious code that poses significant risks to developers and users. It is crucial to update or remove this package to protect your projects from potential exploitation. Utilizing tools like Vulert can help you stay informed about vulnerabilities in your dependencies.

See every vulnerability recorded for identical_whippet_0xrequest →

Share this vulnerability

FAQ

It is an npm package that has been linked to a campaign aimed at generating and publishing derivative packages for token rewards.

The malicious code can modify your package.json, remove private flags, and lead to the installation of unwanted or harmful packages.

You should immediately update the package to a secure version or remove it from your project to mitigate any risks.

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

Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without signing up.

How To Fix

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

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