Malicious Code Injection in confidential_mite_dumbs Package

confidential_mite_dumbs Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-100842: Malicious code in confidential_mite_dumbs (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 Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

Background

The 'confidential_mite_dumbs' package is part of a broader ecosystem within the npm registry, often associated with token reward campaigns. These packages are designed to automate the generation and publication of derivative packages, which can mislead developers and inflate reputation scores. The malicious nature of this package lies in its ability to modify critical files and republish variants, thereby polluting the npm registry.

Vulnerability Detail

The vulnerability originates from a malicious payload embedded within the 'confidential_mite_dumbs' package. This payload alters the package.json file by removing private flags, changing version numbers, and generating random package names. The continuous republishing of these variants can lead to a cluttered npm registry, making it difficult for developers to find legitimate packages. The potential ramifications include compromised developer reputations and the risk of inadvertently using malicious packages in projects.

How To Fix

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

npm uninstall confidential_mite_dumbs

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 measure, you can avoid using the 'confidential_mite_dumbs' package altogether. If you have already installed it, ensure to monitor your package.json and package-lock.json files for any unauthorized changes. Regularly audit your dependencies using tools like npm audit.

Conclusion

The 'confidential_mite_dumbs' package poses a significant risk due to its malicious code designed to manipulate package metadata and republish variants. It is crucial for developers to remain vigilant, regularly audit their dependencies, and utilize tools like Vulert to monitor for vulnerabilities. Taking immediate action to remove this package can help safeguard your projects.

See every vulnerability recorded for confidential_mite_dumbs →

Share this vulnerability

FAQ

It is an npm package associated with malicious activities, primarily designed to inflate developer reputation scores through automated publishing.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Check your application against the vulnerability using the Vulert playground at Vulert Scanner.

Using this package can lead to unauthorized modifications of your project files, potential security risks, and a polluted npm registry.

Regularly audit your dependencies, use trusted sources for packages, and consider implementing automated tools that monitor for vulnerabilities.

Remove the package immediately and audit your project for any changes made by the malicious payload. Update your dependencies as necessary.

Sponsored Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

How To Fix

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

npm uninstall confidential_mite_dumbs

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