Malicious Code Injection in mand-nofoayif-mutu Package: A Threat to npm Ecosystem

mand-nofoayif-mutu Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-159590: Malicious code in mand-nofoayif-mutu (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 mand-nofoayif-mutu package is part of the npm ecosystem, primarily used for JavaScript and Node.js applications. It is designed to facilitate various functionalities within projects. However, this package has been identified as part of a malicious campaign that floods the npm registry with derivative packages, compromising the integrity of the ecosystem.

Vulnerability Detail

The vulnerability originates from the mand-nofoayif-mutu package being associated with the tea.xyz token reward campaign. This campaign employs malicious scripts that automatically modify the package.json file, removing private flags and changing version numbers. It generates random package names and continuously republishes these variants, which can lead to pollution of the npm registry 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 mand-nofoayif-mutu

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 mand-nofoayif-mutu package and look for alternative packages that provide similar functionality without the associated risks. Additionally, regularly audit your npm packages using tools like npm audit to identify and mitigate vulnerabilities.

Conclusion

The mand-nofoayif-mutu package poses a significant threat to the npm ecosystem due to its malicious behavior. It is crucial for developers to be vigilant, remove affected packages, and utilize tools to monitor for vulnerabilities to maintain the integrity of their projects.

See every vulnerability recorded for mand-nofoayif-mutu →

Share this vulnerability

FAQ

The mand-nofoayif-mutu package is an npm package that has been identified as part of a malicious campaign aimed at inflating developer reputation scores through the creation of derivative packages.

This vulnerability can lead to the pollution of the npm registry, potentially affecting your project's dependencies and compromising the integrity of your application.

If you have installed the mand-nofoayif-mutu package, it is recommended to uninstall it immediately and check for any dependencies that may be affected.

You can use tools like npm audit to check for vulnerabilities in your npm packages. Additionally, Vulert can monitor your package-lock.json file to alert you in real-time for any open-source vulnerabilities.

Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring any signup.

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 mand-nofoayif-mutu

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