Malicious Code Injection in mwjaul-devapptea Package

mwjaul-devapptea Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-106067: Malicious code in mwjaul-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 mwjaul-devapptea package is part of the npm ecosystem, typically used in various JavaScript applications. It is associated with the tea.xyz token reward campaign, which has been known to flood the npm registry with numerous packages. These packages often contain scripts that automatically generate and publish derivative packages, which can lead to reputation inflation for developers involved in the tea protocol.

Vulnerability Detail

The mwjaul-devapptea package contains malicious code that modifies the package.json file by removing private flags, altering version numbers, and generating random package names. This behavior is part of a broader scheme to pollute the npm registry by continuously republishing variants of the package. The origin of this vulnerability is linked to the tea.xyz token reward campaign, which incentivizes developers to inflate their reputation scores through such malicious practices. The ramifications include potential security risks for applications using this package, as well as the degradation of the npm registry's integrity.

How To Fix

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

npm uninstall mwjaul-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 mwjaul-devapptea package altogether and look for alternative packages that provide similar functionality without the associated risks. Additionally, you can monitor your project for any dependencies that may introduce vulnerabilities using tools like Vulert, which can alert you to open-source vulnerabilities in real-time.

Conclusion

The mwjaul-devapptea package poses a significant security risk due to its malicious code that modifies package configurations and pollutes the npm registry. It is crucial for developers to remove this package from their projects and utilize tools like Vulert to monitor for vulnerabilities in their dependencies.

See every vulnerability recorded for mwjaul-devapptea →

Share this vulnerability

FAQ

The mwjaul-devapptea package is an npm package associated with the tea.xyz token reward campaign, often used in JavaScript applications.

The package modifies the package.json file, removes private flags, changes version numbers, and generates random package names to pollute the npm registry.

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

If you have installed the mwjaul-devapptea package, you should uninstall it immediately using the command npm uninstall mwjaul-devapptea.

Yes, Vulert can monitor your project for open-source vulnerabilities in real-time using just your package-lock.json file.

How To Fix

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

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