Malicious Code Vulnerability in mutual_tortoise_dumbs Package

mutual_tortoise_dumbs Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-106064: Malicious code in mutual_tortoise_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 MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

The mutual_tortoise_dumbs package is part of the npm ecosystem, which is widely used for JavaScript package management. This package has been identified as part of a malicious campaign that aims to exploit npm's publishing capabilities. It is designed to generate and publish derivative packages with randomized names, thereby inflating developer reputation scores for token rewards in the tea.xyz protocol. The malicious behavior of this package poses a significant risk to developers and the integrity of the npm registry.

Vulnerability Detail

The vulnerability originates from the malicious code embedded within the mutual_tortoise_dumbs package. This code modifies the package.json file by removing private flags, altering version numbers, and generating random package names. It continuously republishes these variants, leading to pollution of the npm registry and potential misuse of developer accounts. The ramifications include compromised package integrity, increased risk of dependency confusion, and potential exploitation of developers' reputations.

How To Fix

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

npm uninstall mutual_tortoise_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 avoid using the mutual_tortoise_dumbs package and any packages that depend on it. Regularly audit your package-lock.json file to identify and remove any instances of this malicious package.

Conclusion

The mutual_tortoise_dumbs package poses a significant threat to developers and the npm ecosystem due to its malicious behavior. It is essential to take immediate action to remove this package and implement best practices for dependency management to safeguard your projects.

See every vulnerability recorded for mutual_tortoise_dumbs →

Share this vulnerability

FAQ

The mutual_tortoise_dumbs package is a malicious npm package that is part of a campaign to exploit the npm registry by generating and publishing derivative packages.

This vulnerability can compromise the integrity of your project by introducing malicious code and potentially damaging your developer reputation.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. By using the Vulert playground, you can check if your application is affected without any signup.

You should immediately uninstall the mutual_tortoise_dumbs package and review your project for any other potentially malicious dependencies.

Regularly audit your dependencies, keep your packages updated, and use tools like Vulert to monitor for vulnerabilities in your open-source software.

How To Fix

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

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