Malicious Code Injection in gprrxf-devapptea Package

gprrxf-devapptea Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-103322: Malicious code in gprrxf-devapptea (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 gprrxf-devapptea package is part of the tea.xyz token reward campaign that has infiltrated the npm ecosystem. This package is designed to facilitate the generation and publication of derivative packages, often with randomized names, to inflate developer reputation scores for token rewards. Its functionality is compromised by malicious scripts that manipulate package metadata.

Vulnerability Detail

The vulnerability in the gprrxf-devapptea package stems from its inclusion in a campaign that floods the npm registry with malicious packages. These packages contain scripts that modify the package.json file to remove private flags, change version numbers, and generate random names, leading to the continuous republishing of variants. This not only pollutes the npm registry but also poses a risk 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 gprrxf-devapptea

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 prevent the installation of this package by using npm's package-lock.json to monitor dependencies. If you are using Vulert, you can check your application for vulnerabilities without any installation. Simply visit the Vulert playground at https://vulert.com/scanner and upload your package-lock.json file to see if your application is affected.

Conclusion

The gprrxf-devapptea package poses a significant risk due to its malicious code designed to manipulate npm packages. It is essential to remove this package from your projects and utilize tools like Vulert to monitor for vulnerabilities effectively. Staying informed and proactive is key to maintaining the security of your applications.

See every vulnerability recorded for gprrxf-devapptea →

Share this vulnerability

FAQ

gprrxf-devapptea is a package associated with the tea.xyz token reward campaign, designed to generate and publish derivative packages in the npm registry.

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

You should immediately remove the gprrxf-devapptea package from your project and monitor for any updates or patches that may be released.

Yes, you can use Vulert to monitor your package-lock.json for vulnerabilities in real-time without needing to install any software.

You can find detailed information about this vulnerability in the official npm registry or by visiting the Vulert website.

How To Fix

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

npm uninstall gprrxf-devapptea

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