Malicious Code Injection in dear_dormouse-notthedev Package

dear_dormouse-notthedev Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-101237: Malicious code in dear_dormouse-notthedev (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 dear_dormouse-notthedev package is part of the npm ecosystem, typically used for various development tasks. However, it has been identified as part of a malicious campaign that exploits npm's publishing capabilities. This package is designed to inflate developer reputation scores through the automatic generation and publishing of derivative packages, which can lead to significant pollution of the npm registry.

Vulnerability Detail

The vulnerability stems from the package's involvement in the tea.xyz token reward campaign, which has been flooding the npm registry with malicious packages. The malicious code modifies the package.json file by removing private flags, altering version numbers, and generating random package names. This behavior not only compromises the integrity of the affected package but also poses a risk to the entire npm ecosystem by polluting the registry with potentially harmful derivatives.

How To Fix

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

npm uninstall dear_dormouse-notthedev

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 this package by using npm's package-lock.json to monitor dependencies. Ensure that your project does not include dear_dormouse-notthedev in its dependencies.

Conclusion

The dear_dormouse-notthedev package has been identified as a malicious entity within the npm ecosystem, posing significant risks to developers and their applications. It is crucial to take immediate action to remove this package and monitor for similar vulnerabilities in the future.

See every vulnerability recorded for dear_dormouse-notthedev →

Share this vulnerability

FAQ

The package contains malicious code that modifies package.json and floods the npm registry with derivative packages.

You can use Vulert's playground at Vulert Scanner to check if your application is affected without requiring any signup.

You should remove the package from your project and consider using a safer alternative.

Regularly monitor your dependencies using tools like Vulert, which can alert you to open-source vulnerabilities in real-time.

Using compromised packages can lead to security breaches, data loss, and the introduction of malicious code into your applications.

How To Fix

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

npm uninstall dear_dormouse-notthedev

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