Malicious Code Injection in Grateful Jaguar 0xRequest Package

grateful_jaguar_0xrequest Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-103354: Malicious code in grateful_jaguar_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 'grateful_jaguar_0xrequest' package is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to facilitate token rewards through various automated scripts. However, it has been identified as containing malicious code that compromises its integrity and the security of applications that depend on it.

Vulnerability Detail

The vulnerability originates from the package's malicious payload, which modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior is intended to inflate developer reputation scores and pollute the npm registry with derivative packages. The ramifications include potential exposure of sensitive data, unauthorized access to systems, and degradation of the npm ecosystem.

How To Fix

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

npm uninstall grateful_jaguar_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 remove the 'grateful_jaguar_0xrequest' package from your project by executing: 'npm uninstall grateful_jaguar_0xrequest'. Additionally, consider using alternative packages that provide similar functionality without the associated risks.

Conclusion

The 'grateful_jaguar_0xrequest' package poses significant security risks due to its malicious code. It is crucial for developers to take immediate action by updating or removing the package to safeguard their applications. Utilizing tools like Vulert can help in monitoring and managing vulnerabilities effectively.

See every vulnerability recorded for grateful_jaguar_0xrequest →

Share this vulnerability

FAQ

It is an npm package associated with the tea.xyz token reward campaign, designed to automate the generation and publication of derivative packages.

The malicious code can modify your package.json, remove private flags, and publish unauthorized packages, potentially leading to security vulnerabilities.

You should immediately update or uninstall the package to prevent any security risks associated with its malicious behavior.

Yes, you can use tools like Vulert, which monitors and alerts for open-source vulnerabilities in your software by analyzing your package-lock.json.

You can use the Vulert playground at Vulert Scanner to check if your application is affected without needing to sign up.

How To Fix

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

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