Malicious Code Vulnerability in tqkmnh-devapptea Package

tqkmnh-devapptea Updated 18 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-109796: Malicious code in tqkmnh-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 Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

Background

The tqkmnh-devapptea package is part of the tea.xyz token reward campaign that has infiltrated the npm ecosystem. It is designed to facilitate the automatic generation and publication of derivative packages, which can inflate developer reputation scores in exchange for tea protocol token rewards. This package is particularly concerning due to its ability to modify critical files and republish malicious variants, thereby polluting the npm registry.

Vulnerability Detail

The vulnerability in the tqkmnh-devapptea package stems from its 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 create numerous derivative packages that can mislead users and inflate the reputation of the package's authors. The origin of this vulnerability is linked to the tea.xyz token reward campaign, which exploits npm's publishing mechanisms to distribute harmful packages.

How To Fix

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

npm uninstall tqkmnh-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 avoid using the tqkmnh-devapptea package and any packages that depend on it. Regularly audit your dependencies using tools like npm audit to identify and mitigate potential vulnerabilities.

Conclusion

The tqkmnh-devapptea package poses a significant risk due to its malicious code that alters critical project files and repopulates the npm registry with harmful variants. It is essential to take immediate action by removing this package and employing tools like Vulert for ongoing vulnerability monitoring.

See every vulnerability recorded for tqkmnh-devapptea →

Share this vulnerability

FAQ

The tqkmnh-devapptea package is part of a campaign that aims to exploit npm by generating and publishing numerous derivative packages for token rewards.

The vulnerability can lead to the modification of your package.json file, potentially exposing your project to further risks and pollution of the npm registry.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. By uploading your package-lock.json file, you can quickly assess if your application is impacted.

If you have installed tqkmnh-devapptea, it is crucial to uninstall it immediately using npm uninstall tqkmnh-devapptea and check for any other affected packages.

Regularly audit your dependencies, use tools like npm audit, and consider using Vulert to monitor your projects for vulnerabilities.

Sponsored Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

How To Fix

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

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