Malicious Code Injection in mahnud-nofit-gamoani: A Threat to npm Packages

mahnud-nofit-gamoani Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-159081: Malicious code in mahnud-nofit-gamoani (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 package 'mahnud-nofit-gamoani' is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This campaign has been known to flood the npm registry with packages that contain scripts designed to inflate developer reputation scores through the automatic generation and publication of derivative packages. The malicious nature of this package lies in its ability to modify critical files and republish variants, thereby polluting the npm registry.

Vulnerability Detail

The vulnerability in 'mahnud-nofit-gamoani' originates from its malicious payload, which modifies the package.json file to remove private flags and alters version numbers. It generates random package names, often themed around Indonesian culture, and continuously republishes these variants. This behavior not only compromises the integrity of the npm registry but also poses risks to developers who may unknowingly use these tainted packages, leading to potential security breaches and reputation damage.

How To Fix

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

npm uninstall mahnud-nofit-gamoani

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 remove the 'mahnud-nofit-gamoani' package from your project by executing the command: 'npm uninstall mahnud-nofit-gamoani'. This will prevent any malicious scripts from executing until a secure version is available.

Conclusion

The 'mahnud-nofit-gamoani' package presents a significant security risk due to its malicious code that alters package configurations and repopulates the npm registry with tainted versions. It is crucial to take immediate action by updating or removing the package to safeguard your projects.

See every vulnerability recorded for mahnud-nofit-gamoani →

Share this vulnerability

FAQ

The main risk is the potential for malicious code execution that can compromise your project's integrity and security.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check your application without any signup.

If an immediate update is not possible, consider removing the package from your project as a temporary measure.

While specific exploits have not been detailed, the nature of the vulnerability allows for significant risks, including unauthorized access and data manipulation.

Regularly audit your dependencies, use tools like Vulert for monitoring, and stay updated on security advisories related to the packages you use.

How To Fix

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

npm uninstall mahnud-nofit-gamoani

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