Malicious Code Injection in mjiqrr-devapptea: A Threat to npm Ecosystem

mjiqrr-devapptea Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-105908: Malicious code in mjiqrr-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 Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

mjiqrr-devapptea is an npm package that is part of the tea.xyz token reward campaign. This package is designed to facilitate token rewards by generating and publishing derivative packages. However, it has been identified as malicious, containing scripts that manipulate package metadata and flood the npm registry with unwanted packages.

Vulnerability Detail

The vulnerability originates from the package's design, which includes autopublish scripts that modify the package.json file. These scripts remove private flags, alter version numbers, and create random package names, leading to the pollution of the npm registry. This not only affects the integrity of the npm ecosystem but can also inflate developer reputation scores fraudulently, posing a risk to developers and users relying on npm packages.

How To Fix

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

npm uninstall mjiqrr-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 mjiqrr-devapptea package entirely and look for alternative packages that provide similar functionality without the associated risks.

Conclusion

The mjiqrr-devapptea package poses a significant threat to the npm ecosystem due to its malicious code that manipulates package metadata. It is crucial for developers to uninstall this package and monitor their projects for vulnerabilities to maintain the integrity of their applications.

See every vulnerability recorded for mjiqrr-devapptea →

Share this vulnerability

FAQ

mjiqrr-devapptea is an npm package involved in the tea.xyz token reward campaign, which has been identified as malicious.

The vulnerability can lead to the pollution of the npm registry and may compromise the integrity of your project by introducing unwanted packages.

You should uninstall the mjiqrr-devapptea package immediately using 'npm uninstall mjiqrr-devapptea'.

Yes, consider looking for other npm packages that offer similar functionality without the associated risks.

You can use Vulert to monitor your project for open-source vulnerabilities. It uses package-lock.json to provide real-time alerts. You can check if your application is affected by this vulnerability using the Vulert playground at Vulert Scanner.

How To Fix

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

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