Malicious Code Injection in mutssrio-muiko-muyiaf Package

mutssrio-muiko-muyiaf Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-161181: Malicious code in mutssrio-muiko-muyiaf (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 mutssrio-muiko-muyiaf 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 the npm registry by flooding it with derivative packages. These packages are designed to inflate developer reputation scores for token rewards associated with the tea.xyz protocol. The vulnerability arises from the package's malicious scripts that alter its own metadata and republish variants, leading to potential security risks for developers using it.

Vulnerability Detail

The vulnerability in the mutssrio-muiko-muyiaf package originates from its association with a malicious campaign that modifies the package.json file to remove private flags and changes version numbers. It generates random package names and continuously republishes these variants, polluting the npm registry. This behavior can lead to developers inadvertently using compromised packages, which may contain harmful code or lead to reputation damage in the npm community.

How To Fix

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

npm uninstall mutssrio-muiko-muyiaf

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 workaround, you can avoid using the mutssrio-muiko-muyiaf package altogether and look for alternative packages that provide similar functionality without the associated risks. Additionally, consider using tools like Vulert to monitor your project for vulnerabilities. You can check if your application is affected by this vulnerability using the Vulert playground at https://vulert.com/scanner without any signup.

Conclusion

The mutssrio-muiko-muyiaf package poses a significant risk due to its malicious behavior of altering package metadata and republishing variants. It is crucial for developers to remove this package from their projects and utilize tools like Vulert to monitor for vulnerabilities in real-time. Staying informed and proactive can help mitigate the risks associated with open-source dependencies.

See every vulnerability recorded for mutssrio-muiko-muyiaf →

Share this vulnerability

FAQ

The mutssrio-muiko-muyiaf package is an npm package that has been identified as part of a malicious campaign to exploit the npm registry.

This vulnerability can lead to the inclusion of malicious code in your project, potentially compromising security and damaging your reputation in the npm community.

You should uninstall the mutssrio-muiko-muyiaf package immediately and check your project for any other compromised packages.

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

Yes, you can use the Vulert playground at Vulert Scanner to check for vulnerabilities in your application without needing to sign up.

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 mutssrio-muiko-muyiaf

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