Malicious Code Injection in muy-mutfru-muytio Package - npm Vulnerability

muy-mutfru-muytio Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-161190: Malicious code in muy-mutfru-muytio (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 muy-mutfru-muytio package is part of the npm ecosystem, often utilized in JavaScript applications for various functionalities. However, it has been identified as part of a malicious campaign that floods the npm registry with derivative packages aimed at inflating developer reputation scores for token rewards. This package, like others in the campaign, contains scripts that automate the generation and publication of these malicious packages.

Vulnerability Detail

The vulnerability stems from the presence of malicious code within the muy-mutfru-muytio package. This code modifies the package.json file to remove private flags, alters version numbers, and generates random package names, thereby polluting the npm registry. The origin of this issue is linked to a token reward campaign that exploits npm's publishing capabilities, leading to potential security risks for 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 muy-mutfru-muytio

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 muy-mutfru-muytio package and any other packages associated with the tea.xyz token reward campaign. Monitor your package-lock.json file for any unauthorized changes and consider using tools like Vulert to keep track of vulnerabilities.

Conclusion

The muy-mutfru-muytio package poses a significant security risk due to its malicious code designed to manipulate npm's publishing system. Developers should take immediate action to remove this package and monitor their dependencies for similar vulnerabilities. Utilizing tools like Vulert can help maintain the security of your projects.

See every vulnerability recorded for muy-mutfru-muytio →

Share this vulnerability

FAQ

muy-mutfru-muytio is an npm package that has been identified as part of a malicious campaign aimed at inflating developer reputation scores through the publication of derivative packages.

If your project includes the muy-mutfru-muytio package, it may be at risk of being polluted with malicious code, which can lead to security vulnerabilities and potential exploitation.

You should uninstall the muy-mutfru-muytio package immediately using npm uninstall muy-mutfru-muytio and review your project's dependencies for any other potentially malicious packages.

You can use tools like Vulert, which monitors your package-lock.json file for open-source vulnerabilities in real-time without requiring code access or installation.

There is no patch for the muy-mutfru-muytio package itself due to its malicious nature. The best course of action is to remove it from your project.

How To Fix

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

npm uninstall muy-mutfru-muytio

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