Malicious Code Injection in mahnud-magu-nuam Package

mahnud-magu-nuam Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-159055: Malicious code in mahnud-magu-nuam (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

The mahnud-magu-nuam package is part of the npm ecosystem and has been identified as a component of a malicious campaign targeting developers. This package is designed to automate the generation and publication of derivative packages, which can inflate developer reputation scores in exchange for token rewards. Its functionality is compromised due to the presence of malicious scripts that manipulate package metadata.

Vulnerability Detail

The vulnerability originates from the package being part of a malicious campaign that floods the npm registry with derivative packages. The malicious payload alters the package.json file by removing private flags, changing version numbers, and generating random package names. This behavior not only pollutes the npm registry but also poses a risk to developers who may unknowingly use these compromised packages, leading to potential security breaches and loss of reputation.

How To Fix

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

npm uninstall mahnud-magu-nuam

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 workaround, avoid using the mahnud-magu-nuam package and any other packages that are part of the tea.xyz token reward campaign. Regularly audit your dependencies using tools like Vulert to monitor for vulnerabilities. You can check if your application is affected by this vulnerability using the Vulert playground at https://vulert.com/scanner without needing to sign up.

Conclusion

The mahnud-magu-nuam package poses a significant risk due to its malicious code designed to manipulate package metadata and pollute the npm registry. It is essential for developers to remove this package from their projects and utilize tools like Vulert to monitor for vulnerabilities. Staying informed and proactive can help mitigate the risks associated with open-source packages.

See every vulnerability recorded for mahnud-magu-nuam →

Share this vulnerability

FAQ

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

This vulnerability can lead to the pollution of the npm registry, potentially exposing your application to security risks and affecting its integrity if compromised packages are used.

If you have installed the mahnud-magu-nuam package, it is recommended to uninstall it immediately using 'npm uninstall mahnud-magu-nuam' and audit your project for any other potentially malicious packages.

You can use tools like Vulert, which monitors your package-lock.json file for open-source vulnerabilities in real-time. You can also check for vulnerabilities using the Vulert playground.

To prevent future vulnerabilities, regularly audit your dependencies, use trusted packages, and stay updated with the latest security advisories from the npm community.

How To Fix

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

npm uninstall mahnud-magu-nuam

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