Malicious Code Injection in ouvhww-devapptea Package

ouvhww-devapptea Updated 18 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-106855: Malicious code in ouvhww-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 ouvhww-devapptea package is part of the tea.xyz token reward campaign, which has been known to flood the npm registry with various packages. This package is designed to facilitate token rewards for developers by automatically generating and publishing derivative packages. However, it has been compromised to include malicious scripts that can manipulate package metadata.

Vulnerability Detail

The vulnerability in the ouvhww-devapptea package arises from the inclusion of malicious code that modifies the package.json file. This code removes private flags, alters version numbers, and generates random package names, leading to the pollution of the npm registry. The malicious payload is designed to inflate developer reputation scores through the automatic publication of these derivative packages, which can have significant ramifications for the integrity of the npm ecosystem.

How To Fix

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

npm uninstall ouvhww-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 prevent the installation of the ouvhww-devapptea package by using npm's package-lock.json to monitor dependencies. You can also use the following command to uninstall the package if it is already installed: npm uninstall ouvhww-devapptea.

Conclusion

The ouvhww-devapptea package contains malicious code that poses a significant risk to developers and the npm ecosystem. It is crucial to remove this package from your projects and to remain vigilant about the packages you use. Utilizing tools like Vulert can help in monitoring and managing open-source vulnerabilities effectively.

See every vulnerability recorded for ouvhww-devapptea →

Share this vulnerability

FAQ

The ouvhww-devapptea package is part of a token reward campaign that aims to incentivize developers through automatic package generation and publication.

The malicious code can alter your project's package.json file, potentially leading to unintended consequences such as the publication of unauthorized packages and the compromise of your project's integrity.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. By using the Vulert playground, you can check if your application is affected without any signup.

If you have installed the ouvhww-devapptea package, it is advisable to uninstall it immediately using the command: npm uninstall ouvhww-devapptea.

To prevent similar vulnerabilities, regularly audit your dependencies, use tools like Vulert for monitoring, and be cautious when installing packages from unknown sources.

How To Fix

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

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