Malicious Code Injection in grand_gerbil_0xrequest Package

grand_gerbil_0xrequest Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-103342: Malicious code in grand_gerbil_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 grand_gerbil_0xrequest package is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to facilitate various functionalities related to token rewards but has been compromised. It is known for generating and publishing derivative packages with randomized names, which can inflate developer reputation scores. Unfortunately, this package has been exploited to introduce malicious scripts that affect its integrity and the npm registry.

Vulnerability Detail

The vulnerability in the grand_gerbil_0xrequest package stems from its association with malicious scripts that modify the package.json file. These scripts remove private flags, alter version numbers, and generate random package names, leading to the continuous republishing of these variants. This behavior not only pollutes the npm registry but also poses significant risks to developers who may unknowingly use these compromised packages, potentially leading to security breaches in their applications.

How To Fix

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

npm uninstall grand_gerbil_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 grand_gerbil_0xrequest package until a fix is released. Additionally, you can monitor your package-lock.json file for any changes that may indicate the presence of malicious code. Regularly auditing your dependencies can help identify and mitigate risks.

Conclusion

The grand_gerbil_0xrequest package has been compromised with malicious code that alters its functionality and can affect developers using it. It is essential to take immediate action by updating or removing the package to safeguard your applications. Regular monitoring of dependencies is crucial for maintaining security.

See every vulnerability recorded for grand_gerbil_0xrequest →

Share this vulnerability

FAQ

The grand_gerbil_0xrequest package is an npm package associated with the tea.xyz token reward campaign, designed to facilitate token-related functionalities.

The vulnerability can lead to the introduction of malicious code in your application, potentially compromising its security and integrity.

If you are using the grand_gerbil_0xrequest package, you should update it to the latest patched version or remove it from your project until a fix is available.

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

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 grand_gerbil_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