Malicious Code Injection in mahnud-magu-nami: A Threat to npm Ecosystem

mahnud-magu-nami Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-159052: Malicious code in mahnud-magu-nami (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 Devnack Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

mahnud-magu-nami is an npm package that has been identified as part of a malicious campaign targeting the npm ecosystem. This package is associated with the tea.xyz token reward initiative, which has been known to flood the npm registry with derivative packages. The primary functionality of this package is to serve as a vehicle for malicious scripts that manipulate package metadata and inflate developer reputation scores.

Vulnerability Detail

The vulnerability in mahnud-magu-nami stems from its inclusion in a malicious campaign that employs scripts to modify package.json files. These scripts remove private flags, alter version numbers, and generate random package names, leading to the continuous republishing of variants. This behavior not only pollutes the npm registry but also poses a risk to developers who may unknowingly install these compromised packages, potentially leading to security breaches in their applications.

How To Fix

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

npm uninstall mahnud-magu-nami

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-magu-nami package and look for alternative packages that provide similar functionality without the associated risks. Additionally, you can use tools like Vulert to monitor your package-lock.json for vulnerabilities. To check if your application is affected by this vulnerability, you can visit the Vulert playground at https://vulert.com/scanner without any signup.

Conclusion

The mahnud-magu-nami package poses a significant risk due to its malicious code that alters package metadata and inflates developer reputation scores. It is crucial for developers to be vigilant, regularly update their dependencies, and utilize tools like Vulert to safeguard their applications from such vulnerabilities.

See every vulnerability recorded for mahnud-magu-nami →

Share this vulnerability

FAQ

mahnud-magu-nami is an npm package that has been identified as part of a malicious campaign aimed at inflating developer reputation scores through the publication of derivative packages.

The vulnerability can lead to the installation of malicious code that modifies your package.json, potentially compromising your application's integrity and security.

You should uninstall the mahnud-magu-nami package immediately and review your other dependencies for any potential vulnerabilities.

Yes, regularly update your packages, use tools like Vulert to monitor for vulnerabilities, and review your dependencies for any suspicious activity.

Vulert is a tool that monitors your package-lock.json for open-source vulnerabilities in real-time. You can use it to check if your application is affected by known vulnerabilities without needing to install any software.

How To Fix

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

npm uninstall mahnud-magu-nami

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