Malicious Code Injection in man-nonatai-agamiga Package: A Threat to npm Users

man-nonatai-agamiga Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-159282: Malicious code in man-nonatai-agamiga (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 man-nonatai-agamiga package is part of the npm ecosystem, which is widely used for JavaScript package management. This package is associated with the tea.xyz token reward campaign, which has been known to flood the npm registry with malicious packages. The primary function of such packages is to manipulate developer reputation scores through automated publishing of derivative packages.

Vulnerability Detail

The vulnerability in the man-nonatai-agamiga package originates from its malicious code designed to modify the package.json file. This code removes private flags, alters version numbers, and generates random package names, leading to the pollution of the npm registry. The ramifications include potential security risks for developers who unknowingly install these packages, as they may inadvertently expose their projects to further vulnerabilities or malicious activities.

How To Fix

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

npm uninstall man-nonatai-agamiga

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 avoid using the man-nonatai-agamiga package and monitor your package-lock.json file for any unauthorized changes. Additionally, consider using tools like Vulert to monitor your dependencies for vulnerabilities.

Conclusion

The man-nonatai-agamiga package poses a significant threat due to its malicious code designed to manipulate npm packages. It is essential for developers to be vigilant and remove any affected packages while utilizing tools like Vulert to monitor for vulnerabilities in their projects.

See every vulnerability recorded for man-nonatai-agamiga →

Share this vulnerability

FAQ

It is an npm package that has been identified as malicious, associated with automated publishing scripts that inflate developer reputation scores.

If you have this package installed, it can modify your package.json file and potentially expose your project to further vulnerabilities.

You should uninstall the man-nonatai-agamiga package immediately and monitor your project for any unauthorized changes.

You can use tools like Vulert, which monitors your package-lock.json file for vulnerabilities in real-time without requiring code access.

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 man-nonatai-agamiga

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