Malicious Code Injection in mbwkje-devapptea Package

mbwkje-devapptea Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-105722: Malicious code in mbwkje-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 mbwkje-devapptea package is part of the tea.xyz token reward campaign that has recently infiltrated the npm ecosystem. This package is designed to facilitate token rewards through the generation and publication of derivative packages. However, it has been identified as containing malicious scripts that compromise its integrity and the security of the npm registry.

Vulnerability Detail

The vulnerability in the mbwkje-devapptea package stems from malicious code that modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior is intended to inflate developer reputation scores for token rewards while polluting the npm registry with numerous derivative packages. The origin of this vulnerability is linked to a broader campaign that exploits npm's publishing mechanisms, posing significant risks to developers and users relying on 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 mbwkje-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 affected package by using the following command to uninstall it: npm uninstall mbwkje-devapptea. Additionally, ensure that your package.json does not include this package to avoid accidental reinstallation.

Conclusion

The mbwkje-devapptea package contains a significant vulnerability due to malicious code that alters package metadata and floods the npm registry with derivative packages. It is essential to take immediate action by updating or uninstalling the package to protect your application and maintain the integrity of your development environment.

See every vulnerability recorded for mbwkje-devapptea →

Share this vulnerability

FAQ

The mbwkje-devapptea package is part of a token reward campaign that generates and publishes derivative packages in the npm ecosystem.

The vulnerability can lead to the modification of your package.json file, potentially compromising your application's integrity and security.

If you have installed the mbwkje-devapptea package, it is recommended to uninstall it immediately and check for any unauthorized changes in your project.

Yes, you can use tools like Vulert, which monitors your package-lock.json for open-source vulnerabilities in real-time without requiring code access or installation.

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

How To Fix

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

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