Malicious Code Injection in mand-nofoaaff-mutunau: A Threat to npm Packages

mand-nofoaaff-mutunau Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-159581: Malicious code in mand-nofoaaff-mutunau (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 package mand-nofoaaff-mutunau is part of a series of npm packages associated with the tea.xyz token reward campaign. These packages are designed to inflate developer reputation scores by automatically generating and publishing derivative packages with randomized names. This behavior not only clutters the npm registry but also poses a significant security risk to developers who may inadvertently use these compromised packages.

Vulnerability Detail

The vulnerability in mand-nofoaaff-mutunau originates from its malicious code that modifies the package.json file. It removes private flags, alters version numbers, and generates random package names, leading to the continuous republishing of variants. This can result in developers unknowingly using compromised packages, which may lead to security breaches and loss of data integrity.

How To Fix

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

npm uninstall mand-nofoaaff-mutunau

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, avoid using the mand-nofoaaff-mutunau package and monitor your dependencies for any instances of this package. You can also utilize tools like Vulert to scan your package-lock.json file for vulnerabilities. To check if your application is affected, visit the Vulert playground at https://vulert.com/scanner.

Conclusion

The mand-nofoaaff-mutunau package poses a significant security risk due to its malicious code designed to manipulate package metadata and inflate reputation scores. It is crucial for developers to remove this package and monitor their dependencies to maintain the integrity of their projects.

See every vulnerability recorded for mand-nofoaaff-mutunau →

Share this vulnerability

FAQ

mand-nofoaaff-mutunau is an npm package that is part of a malicious campaign to inflate developer reputation scores through automated package publishing.

The vulnerability can lead to the inclusion of malicious code in your project, potentially compromising security and data integrity.

If you have installed mand-nofoaaff-mutunau, you should uninstall it immediately using 'npm uninstall mand-nofoaaff-mutunau' and monitor your dependencies for any further issues.

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

Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability 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 mand-nofoaaff-mutunau

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