Malicious Code Injection in jwuvzy-devapptea: A Threat to npm Ecosystem

jwuvzy-devapptea Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-104744: Malicious code in jwuvzy-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

jwuvzy-devapptea is an npm package that is part of the tea.xyz token reward campaign. This package is designed to facilitate the distribution of token rewards through various applications. However, it has been identified as malicious, containing scripts that manipulate package metadata and publish unauthorized derivatives, thereby compromising the integrity of the npm registry.

Vulnerability Detail

The vulnerability in jwuvzy-devapptea stems from its inclusion in a campaign that floods the npm registry with malicious packages. The package contains scripts that modify the package.json file to remove private flags, alter version numbers, and generate random package names. This behavior not only inflates developer reputation scores but also leads to pollution of the npm registry, making it difficult for developers to find legitimate packages. The malicious payload can potentially expose users to further security risks and undermine trust in the npm ecosystem.

How To Fix

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

npm uninstall jwuvzy-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 jwuvzy-devapptea package altogether and look for alternative packages that provide similar functionality without the associated risks. Additionally, you can monitor your project for vulnerabilities using tools like Vulert, which analyzes your package-lock.json file for any open-source vulnerabilities.

Conclusion

The jwuvzy-devapptea package poses a significant threat to the npm ecosystem due to its malicious code that alters package metadata and publishes unauthorized derivatives. It is essential for developers to remove this package from their projects and utilize monitoring tools like Vulert to stay informed about potential vulnerabilities.

See every vulnerability recorded for jwuvzy-devapptea →

Share this vulnerability

FAQ

jwuvzy-devapptea is an npm package associated with the tea.xyz token reward campaign, which has been identified as containing malicious code.

The malicious code modifies your package.json file, removes private flags, and publishes unauthorized derivative packages, potentially compromising your project's integrity.

You should uninstall the package immediately using npm uninstall jwuvzy-devapptea and check your package-lock.json for any references to it.

Yes, you can use Vulert to monitor your project for open-source vulnerabilities in real-time by analyzing your package-lock.json file.

Regularly audit your dependencies, use tools like Vulert for real-time monitoring, and stay informed about known vulnerabilities in the npm ecosystem.

How To Fix

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

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