Malicious Code Injection in mahnud-magufu-goi Package

mahnud-magufu-goi Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-159064: Malicious code in mahnud-magufu-goi (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 mahnud-magufu-goi 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 exploit developers by flooding the npm registry with derivative packages. These packages are designed to inflate developer reputation scores through automated publishing scripts, which can lead to significant pollution of the npm registry and potential security risks for applications relying on these packages.

Vulnerability Detail

The vulnerability in the mahnud-magufu-goi package stems from its inclusion in a malicious campaign that modifies package.json files to remove private flags, changes version numbers, and generates random package names. This behavior is executed through autopublish scripts that continuously republish variants, thereby polluting the npm registry. The ramifications of this vulnerability include compromised package integrity, potential exposure of sensitive information, and the risk of inadvertently using malicious packages in production environments.

How To Fix

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

npm uninstall mahnud-magufu-goi

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, you can temporarily avoid using the mahnud-magufu-goi package and any other packages that may be part of the malicious campaign. Regularly audit your dependencies using tools like npm audit or Vulert to identify and address vulnerabilities in your project.

Conclusion

The mahnud-magufu-goi package poses a significant security risk due to its malicious code that modifies package configurations and floods the npm registry. It is crucial for developers to remove this package and monitor their dependencies for vulnerabilities to maintain the integrity and security of their applications.

See every vulnerability recorded for mahnud-magufu-goi →

Share this vulnerability

FAQ

The mahnud-magufu-goi package is an npm package that has been identified as part of a malicious campaign aimed at exploiting developers by flooding the npm registry with derivative packages.

This vulnerability can compromise the integrity of your application by introducing malicious code, which may lead to security breaches and data exposure.

If you have installed the mahnud-magufu-goi package, you should uninstall it immediately and check your project for any other affected packages.

You can use tools like npm audit or Vulert to monitor your project for open-source vulnerabilities in real-time. Vulert allows you to check your application without requiring access to the code or installation.

Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.

How To Fix

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

npm uninstall mahnud-magufu-goi

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