Malicious Code Injection in mahnud-fuf-goi Package - npm Vulnerability

mahnud-fuf-goi Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-159012: Malicious code in mahnud-fuf-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 Devnack Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

The mahnud-fuf-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 aimed at manipulating developer reputation scores through the tea.xyz token reward system. It is designed to automatically generate and publish derivative packages, which can lead to pollution of the npm registry and compromise the integrity of applications relying on this package.

Vulnerability Detail

The vulnerability originates from the malicious design of the mahnud-fuf-goi package, which includes scripts that modify the package.json file to remove private flags, alter version numbers, and create random package names. This behavior not only inflates developer reputation scores but also poses a risk of introducing untrusted code into applications. The continuous republishing of these variants can lead to a cluttered npm registry, making it difficult for developers to find legitimate packages.

How To Fix

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

npm uninstall mahnud-fuf-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 temporary measure, you can avoid using the mahnud-fuf-goi package and look for alternative packages that provide similar functionality without the associated risks. Always verify the integrity and reputation of packages before including them in your project.

Conclusion

The mahnud-fuf-goi package has been identified as a malicious entity within the npm ecosystem, posing significant risks to applications that utilize it. It is essential for developers to be vigilant about the packages they include in their projects and to take immediate action to remove any malicious packages. Utilizing tools like Vulert can help maintain the security of your dependencies.

See every vulnerability recorded for mahnud-fuf-goi →

Share this vulnerability

FAQ

The mahnud-fuf-goi package is an npm package that has been identified as part of a malicious campaign aimed at manipulating developer reputation scores.

This vulnerability can introduce untrusted code into your application, potentially leading to security breaches and instability.

You should uninstall the mahnud-fuf-goi package immediately using the command npm uninstall mahnud-fuf-goi.

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

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

How To Fix

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

npm uninstall mahnud-fuf-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