Malicious Code Injection in tzgxrf-devapptea Package: A Threat to npm Users

tzgxrf-devapptea Updated 18 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-109906: Malicious code in tzgxrf-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 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 tzgxrf-devapptea package is part of the tea.xyz token reward campaign, which has been known to flood the npm registry with malicious packages. These packages are designed to inflate developer reputation scores through automated scripts that generate and publish derivative packages with randomized names. The presence of such malicious code poses a significant risk to developers and users relying on npm packages for their applications.

Vulnerability Detail

The vulnerability in the tzgxrf-devapptea package originates from its malicious design, which includes autopublish scripts that modify the package.json file to remove private flags, change version numbers, and generate random package names. This behavior leads to the continuous republishing of variants, polluting the npm registry and potentially compromising other packages. The ramifications include loss of trust in the npm ecosystem, potential data breaches, and the risk of integrating compromised packages into applications.

How To Fix

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

npm uninstall tzgxrf-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 workaround, you can manually check your package-lock.json file for any references to tzgxrf-devapptea and remove it. Use the following command to uninstall the package: npm uninstall tzgxrf-devapptea.

Conclusion

The tzgxrf-devapptea package poses a significant threat to npm users due to its malicious code designed to manipulate package data and flood the registry. Immediate action is required to remove this package and safeguard your applications from potential risks.

See every vulnerability recorded for tzgxrf-devapptea →

Share this vulnerability

FAQ

The tzgxrf-devapptea package is part of a malicious campaign that generates and publishes derivative npm packages to inflate developer reputation scores.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software. Check your application against this vulnerability using the Vulert playground at Vulert Scanner.

It is recommended to uninstall the tzgxrf-devapptea package immediately to prevent any potential risks associated with its malicious code.

Yes, using this package can lead to the pollution of the npm registry, loss of trust in the ecosystem, and potential data breaches.

Currently, there is no patched version available. The best course of action is to remove the package from your project.

How To Fix

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

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