Malicious Code Injection in open_mite_requirement Package

open_mite_requirement Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-95752: Malicious code in open_mite_requirement (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

The open_mite_requirement package is part of the npm ecosystem, typically used for managing dependencies in JavaScript applications. It is designed to facilitate the integration of various functionalities within projects. However, this package has been identified as part of a malicious campaign that aims to exploit npm's publishing mechanisms, leading to potential security risks for developers and their applications.

Vulnerability Detail

The vulnerability stems from the malicious code embedded in the open_mite_requirement package, which is linked to a broader campaign involving the tea.xyz token reward system. This code modifies the package.json file by removing private flags, altering version numbers, and generating random package names. The continuous republishing of these variants can lead to pollution of the npm registry, compromising the integrity of the ecosystem and potentially affecting developers who unknowingly integrate these packages into their projects.

How To Fix

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

npm uninstall open_mite_requirement

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, consider removing the open_mite_requirement package from your project until a secure version is released. You can do this by executing the following command: npm uninstall open_mite_requirement. Additionally, you may want to monitor your package-lock.json file for any unauthorized changes.

Conclusion

The open_mite_requirement package has been identified as containing malicious code that poses significant risks to developers and their applications. It is essential to take immediate action by updating or removing the package and utilizing tools like Vulert to monitor for vulnerabilities in your projects.

See every vulnerability recorded for open_mite_requirement →

Share this vulnerability

FAQ

The open_mite_requirement package is an npm package used for managing dependencies in JavaScript applications, but it has been compromised with malicious code.

The malicious code modifies your package.json file, potentially exposing your application to security risks and affecting the integrity of your dependencies.

If you have installed the open_mite_requirement package, it is recommended to uninstall it immediately and monitor for any updates or patches.

You can use Vulert, which monitors your package-lock.json file for open-source vulnerabilities in real-time. Visit https://vulert.com to learn more.

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

How To Fix

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

npm uninstall open_mite_requirement

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