Malicious Code Vulnerability in misleading_egret_dumbs Package

misleading_egret_dumbs Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-105885: Malicious code in misleading_egret_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 Devnack Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The misleading_egret_dumbs package is part of the npm ecosystem, which is widely used for JavaScript package management. This package is associated with the tea.xyz token reward campaign, which has been known to flood npm with malicious packages. Its primary function is to facilitate the automatic generation and publication of derivative packages, often with randomized names, to inflate developer reputation scores for token rewards. This behavior poses significant risks to the integrity of the npm registry.

Vulnerability Detail

The vulnerability in the misleading_egret_dumbs package originates from its design to include autopublish scripts that modify the package.json file. These modifications remove private flags, alter version numbers, and generate random package names, leading to the continuous republishing of variants. This not only pollutes the npm registry but also compromises the security and reliability of the packages available to developers. The malicious payload can potentially allow unauthorized access to sensitive information and disrupt the development process.

How To Fix

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

npm uninstall misleading_egret_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 workaround, you can remove the misleading_egret_dumbs package from your project by executing the following command: npm uninstall misleading_egret_dumbs. This will prevent any malicious activity associated with the package until a secure version is available.

Conclusion

The misleading_egret_dumbs package poses a significant security risk due to its malicious code designed to manipulate package metadata and republish variants. It is crucial for developers to take immediate action by uninstalling the package and monitoring for updates to maintain the integrity of their applications.

See every vulnerability recorded for misleading_egret_dumbs →

Share this vulnerability

FAQ

The misleading_egret_dumbs package is an npm package involved in the tea.xyz token reward campaign, known for flooding the npm registry with malicious packages.

This vulnerability can lead to the pollution of the npm registry, unauthorized access to sensitive information, and potential disruptions in your development process.

If you have the misleading_egret_dumbs package installed, you should uninstall it immediately and monitor for any updates or patches.

Yes, you can use Vulert, which monitors and alerts in real-time for open-source vulnerabilities in your software using just package-lock.json. You can check if your application is affected by this vulnerability using the Vulert playground without any signup.

Regularly update your dependencies, monitor for vulnerabilities using tools like Vulert, and review your package.json and package-lock.json files for any suspicious packages.

How To Fix

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

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