Malicious Code Injection in mand-no-mutunau: npm Package Vulnerability

mand-no-mutunau Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-159576: Malicious code in mand-no-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 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 'mand-no-mutunau' 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 inflate developer reputation scores through the generation of derivative packages. The vulnerability stems from the package's design, which allows for the execution of harmful scripts that can alter package metadata and republish malicious variants.

Vulnerability Detail

The vulnerability in 'mand-no-mutunau' is characterized by the presence of malicious code that modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior is part of a broader scheme associated with the tea.xyz token reward campaign, which aims to manipulate the npm registry by flooding it with derivative packages. The implications of this vulnerability include potential exposure of sensitive data, reputation damage for developers, and pollution of the npm registry with malicious packages.

How To Fix

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

npm uninstall mand-no-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, you can remove the 'mand-no-mutunau' package from your project by executing the command: 'npm uninstall mand-no-mutunau'. This will prevent the execution of any malicious scripts associated with the package until a fix is applied.

Conclusion

The 'mand-no-mutunau' package has been identified as containing malicious code that poses significant risks to developers and the npm ecosystem. It is crucial to take immediate action by updating or uninstalling the package to safeguard your projects. Utilizing tools like Vulert can help monitor and alert for vulnerabilities in real-time.

See every vulnerability recorded for mand-no-mutunau →

Share this vulnerability

FAQ

The vulnerability involves malicious code that modifies package metadata and republished variants to manipulate the npm registry.

You can use Vulert's playground at Vulert Scanner to check if your application is affected without needing to sign up.

Using this package can lead to exposure of sensitive data, damage to your developer reputation, and pollution of the npm registry.

Yes, Vulert offers real-time monitoring and alerts for open-source vulnerabilities using just your package-lock.json file.

If an immediate update is not possible, consider uninstalling the package as a temporary measure to mitigate risks.

How To Fix

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

npm uninstall mand-no-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