Malicious Code Injection in mutiafaft-msiuyu-masdta Package

mutiafaft-msiuyu-masdta Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-161150: Malicious code in mutiafaft-msiuyu-masdta (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 mutiafaft-msiuyu-masdta package is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to automate the generation and publication of derivative packages, which can inflate developer reputation scores. However, it has been identified as containing malicious code that compromises the integrity of the npm registry.

Vulnerability Detail

The vulnerability stems from the malicious payload embedded within the mutiafaft-msiuyu-masdta package. This payload modifies the package.json file to remove private flags, alters version numbers, and generates random package names, thereby flooding the npm registry with potentially harmful packages. The origin of this issue is linked to a broader campaign aimed at exploiting npm for token rewards, which can lead to significant security risks for developers and users relying on the integrity of the npm ecosystem.

How To Fix

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

npm uninstall mutiafaft-msiuyu-masdta

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 measure, avoid using the mutiafaft-msiuyu-masdta package and monitor your project for any dependencies that may indirectly include it. Regularly check your package-lock.json file for any signs of this package and remove it if detected.

Conclusion

The mutiafaft-msiuyu-masdta package poses a significant security risk due to its embedded malicious code. It is crucial for developers to remove this package and monitor their projects for any related vulnerabilities. Utilizing tools like Vulert can help maintain the security of your applications.

See every vulnerability recorded for mutiafaft-msiuyu-masdta →

Share this vulnerability

FAQ

It is an npm package associated with a token reward campaign that automates the publication of derivative packages.

The malicious code can compromise your project's integrity by modifying package.json and flooding the npm registry with harmful packages.

You should uninstall the package immediately using 'npm uninstall mutiafaft-msiuyu-masdta' and check for any other affected packages.

Yes, you can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time using just your package-lock.json file.

You can use the Vulert playground at Vulert Scanner to check for vulnerabilities without needing to sign up.

How To Fix

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

npm uninstall mutiafaft-msiuyu-masdta

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