Malicious Code Injection in qxvfrp-devapptea Package

qxvfrp-devapptea Updated 18 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-107681: Malicious code in qxvfrp-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 Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The qxvfrp-devapptea package is part of the tea.xyz token reward campaign, which has been known to flood the npm registry with various packages. These packages are designed to automate the generation and publication of derivative packages, often with randomized names, to inflate developer reputation scores for token rewards. The package's functionality is compromised due to the presence of malicious scripts that manipulate its metadata.

Vulnerability Detail

The vulnerability in the qxvfrp-devapptea package stems from malicious code that modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior is intended to continuously republish variants, polluting the npm registry and potentially leading to security risks for developers who unknowingly use these compromised packages. The origin of this vulnerability is linked to the tea.xyz token reward campaign, which exploits npm's publishing mechanisms.

How To Fix

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

npm uninstall qxvfrp-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 remove the qxvfrp-devapptea package from your project by executing the following command: npm uninstall qxvfrp-devapptea. This will prevent any malicious code from executing until a secure version is available.

Conclusion

The qxvfrp-devapptea package contains a significant vulnerability due to malicious code that alters its metadata and republishing behavior. It is essential to take immediate action by updating or removing the package to safeguard your project. Utilizing tools like Vulert can help monitor and manage vulnerabilities effectively.

See every vulnerability recorded for qxvfrp-devapptea →

Share this vulnerability

FAQ

qxvfrp-devapptea is a package associated with the tea.xyz token reward campaign, designed to automate the publication of derivative packages.

The vulnerability can lead to the pollution of the npm registry and may compromise the integrity of your project by introducing malicious code.

If you have installed the qxvfrp-devapptea package, it is recommended to uninstall it immediately and check for any updates or patches.

You can use Vulert, which monitors and alerts in real-time for open-source vulnerabilities using just your package-lock.json file. You can also check your application against known vulnerabilities using the Vulert playground.

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

How To Fix

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

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