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

nmqnuh-devapptea Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-106355: Malicious code in nmqnuh-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 package nmqnuh-devapptea is part of the tea.xyz token reward campaign that has recently inundated the npm ecosystem. This package is designed to facilitate the automatic generation and publication of derivative packages, which can mislead developers and inflate reputation scores for token rewards. Its functionality revolves around manipulating package metadata to achieve these ends, making it a significant target for malicious exploitation.

Vulnerability Detail

The vulnerability in nmqnuh-devapptea arises from its malicious payload, which modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior not only pollutes the npm registry but also poses risks to developers who may unknowingly use these compromised packages. The origin of this issue is linked to the broader tea.xyz token reward scheme, which incentivizes such malicious practices.

How To Fix

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

npm uninstall nmqnuh-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 measure, you can avoid using the nmqnuh-devapptea package altogether and monitor your project for any dependencies that may indirectly include it. Regularly audit your package-lock.json file for any unexpected changes or additions.

Conclusion

The nmqnuh-devapptea package poses a significant risk due to its malicious code that alters package metadata and pollutes the npm registry. It is essential for developers to be vigilant, regularly audit their dependencies, and utilize tools like Vulert to monitor for vulnerabilities. By taking proactive measures, you can safeguard your projects from potential threats.

See every vulnerability recorded for nmqnuh-devapptea →

Share this vulnerability

FAQ

nmqnuh-devapptea is an npm package associated with the tea.xyz token reward campaign, designed to generate and publish derivative packages.

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

You should uninstall the package immediately using 'npm uninstall nmqnuh-devapptea' and audit your project for any other compromised dependencies.

You can use tools like Vulert, which monitors your package-lock.json for open-source vulnerabilities in real-time. You can check your application using the Vulert playground without any signup.

Yes, tools like Vulert can help you monitor and alert for vulnerabilities in your npm packages, ensuring your project remains secure.

How To Fix

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

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