Malicious Code Injection in mahnud-unagyu-goi: A Threat to npm Packages

mahnud-unagyu-goi Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-159123: Malicious code in mahnud-unagyu-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

mahnud-unagyu-goi is an npm package that has been identified as part of a malicious campaign targeting the npm registry. This package is associated with the tea.xyz token reward initiative, which aims 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 its own metadata and republish itself under various names, potentially leading to widespread pollution of the npm ecosystem.

Vulnerability Detail

The vulnerability in mahnud-unagyu-goi stems from its malicious payload, which alters the package.json file to remove private flags, changes version numbers, and generates random package names. This behavior is designed to automate the creation and publication of numerous variants of the package, thereby compromising the integrity of the npm registry. The origin of this vulnerability is linked to the tea.xyz token reward campaign, which employs such tactics to manipulate developer reputation metrics. The ramifications include the potential for developers to unknowingly install compromised packages, leading to security risks in their applications.

How To Fix

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

npm uninstall mahnud-unagyu-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 workaround, avoid using the mahnud-unagyu-goi package and consider using alternative packages that provide similar functionality without the associated risks. Always verify the integrity of packages before installation.

Conclusion

The mahnud-unagyu-goi package poses a significant threat due to its malicious behavior of modifying package metadata and republishing itself. It is essential for developers to be vigilant and remove any instances of this package from their projects. Utilizing tools like Vulert can help in monitoring and identifying vulnerabilities in open-source packages.

See every vulnerability recorded for mahnud-unagyu-goi →

Share this vulnerability

FAQ

mahnud-unagyu-goi 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.

The vulnerability can lead to the installation of compromised packages, which may introduce security risks and affect the stability of your application.

If you have installed mahnud-unagyu-goi, you should uninstall it immediately using the command: npm uninstall mahnud-unagyu-goi.

You can use tools like Vulert, which monitors and alerts in real-time for open-source vulnerabilities in your software by analyzing 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-unagyu-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