Malicious Code Detected in oxvtbx-devapptea: npm Package Vulnerability

oxvtbx-devapptea Updated 18 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-106875: Malicious code in oxvtbx-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 MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

The package 'oxvtbx-devapptea' 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 by automatically generating and publishing derivative packages with randomized names. The functionality of this package is compromised due to its malicious intent, which poses a significant risk to developers and users relying on npm packages.

Vulnerability Detail

The vulnerability in 'oxvtbx-devapptea' originates from its inclusion in a campaign that utilizes autopublish scripts to manipulate the npm registry. The malicious payload modifies the package.json file by removing private flags, altering version numbers, and generating random package names. This results in the continuous republishing of variants, which pollutes the npm registry and can lead to security risks for users who inadvertently install these compromised packages.

How To Fix

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

npm uninstall oxvtbx-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, avoid using the 'oxvtbx-devapptea' package and monitor your project for any dependencies that may indirectly include it. You can also utilize tools like Vulert to monitor your package-lock.json for vulnerabilities without requiring code access or installation.

Conclusion

The 'oxvtbx-devapptea' package poses a significant security risk due to its malicious code designed to manipulate the npm registry. Developers should take immediate action to remove this package and monitor their projects for vulnerabilities. Utilizing tools like Vulert can aid in maintaining the security of your software.

See every vulnerability recorded for oxvtbx-devapptea →

Share this vulnerability

FAQ

The main issue is that it contains malicious code designed to manipulate the npm registry and inflate developer reputation scores.

You can use Vulert to check your package-lock.json for vulnerabilities. Visit the Vulert playground at Vulert Scanner to analyze your application.

If you have installed 'oxvtbx-devapptea', you should uninstall it immediately using 'npm uninstall oxvtbx-devapptea' and monitor your dependencies for any related issues.

Currently, there are no patches available for 'oxvtbx-devapptea'. The best course of action is to remove the package entirely.

Vulert monitors your package-lock.json in real-time for open-source vulnerabilities, providing alerts without requiring code access or installation.

How To Fix

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

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