Malicious Code Injection in mjdtpx-devapptea Package

mjdtpx-devapptea Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-105907: Malicious code in mjdtpx-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 mjdtpx-devapptea package is part of the tea.xyz token reward campaign that has infiltrated the npm ecosystem. It is designed to facilitate token rewards through the generation of derivative packages. However, this package has been identified as malicious, containing scripts that manipulate package metadata and publish harmful variants to the npm registry.

Vulnerability Detail

The vulnerability stems from the presence of malicious code within the mjdtpx-devapptea package. This code is designed to automatically modify the package.json file by removing private flags, altering version numbers, and generating random package names. The malicious payload continuously republishes these variants, leading to pollution of the npm registry and potential exploitation of developer reputation scores for token rewards. This poses significant risks, including the potential for dependency confusion and the introduction of further vulnerabilities into dependent projects.

How To Fix

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

npm uninstall mjdtpx-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 mjdtpx-devapptea package altogether. If it is already in use, consider replacing it with a trusted alternative that does not exhibit malicious behavior.

Conclusion

The mjdtpx-devapptea package has been identified as malicious, posing significant risks to projects utilizing it. Immediate action is required to remove this package and monitor for any potential impacts on your application. Utilizing tools like Vulert can help in maintaining the security of your open-source dependencies.

See every vulnerability recorded for mjdtpx-devapptea →

Share this vulnerability

FAQ

mjdtpx-devapptea is a package associated with the tea.xyz token reward campaign, designed to generate and publish derivative packages for token rewards.

The vulnerability can lead to the introduction of malicious code into your project, potentially compromising security and stability.

You should remove the mjdtpx-devapptea package from your project immediately and monitor for any updates or patches.

Yes, you can use Vulert to monitor your project for open-source vulnerabilities in real-time. It analyzes your package-lock.json file without requiring code access.

You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without signing up.

How To Fix

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

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