Malicious Code Injection in mahnud-nofty-mutaigu: A Threat to npm Ecosystem

mahnud-nofty-mutaigu Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-159114: Malicious code in mahnud-nofty-mutaigu (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 'mahnud-nofty-mutaigu' is part of the npm ecosystem, which is widely used for JavaScript package management. This package is linked to the tea.xyz token reward campaign, which has been associated with malicious activities aimed at inflating developer reputation scores. The package's functionality is compromised by the presence of scripts that automate the generation and publication of derivative packages, leading to potential misuse and pollution of the npm registry.

Vulnerability Detail

The vulnerability in 'mahnud-nofty-mutaigu' originates from its association with a malicious campaign that employs scripts to modify package.json files. These modifications include removing private flags, altering version numbers, and generating random package names, which can lead to the proliferation of untrusted packages in the npm registry. The ramifications include a compromised npm ecosystem, potential security risks for developers using these packages, and a degradation of trust in the package management system.

How To Fix

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

npm uninstall mahnud-nofty-mutaigu

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 'mahnud-nofty-mutaigu' package until a secure version is released. Additionally, consider using the following command to uninstall the package: 'npm uninstall mahnud-nofty-mutaigu'. This will help prevent any potential exploitation of the vulnerability.

Conclusion

The 'mahnud-nofty-mutaigu' package poses a significant risk due to its malicious code that alters package metadata and publishes untrusted variants. It is crucial for developers to stay informed about such vulnerabilities and take proactive measures to secure their applications.

See every vulnerability recorded for mahnud-nofty-mutaigu →

Share this vulnerability

FAQ

The vulnerability involves malicious code that modifies package.json files to remove security flags and publish untrusted packages.

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

Using compromised packages can lead to security breaches, data leaks, and a loss of trust in the npm ecosystem.

Yes, Vulert can monitor and alert you in real-time for open-source vulnerabilities using just your package-lock.json.

If immediate updates are not possible, consider uninstalling the package and monitoring for updates regularly.

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 mahnud-nofty-mutaigu

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