Malicious Code Injection in man-nonatai-autgiag Package - npm Vulnerability

man-nonatai-autgiag Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-159285: Malicious code in man-nonatai-autgiag (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 man-nonatai-autgiag package is part of the npm ecosystem and appears to be associated with the tea.xyz token reward campaign. This package is designed to facilitate the automatic generation and publication of derivative packages, which are often used to inflate developer reputation scores for token rewards. Its functionality includes creating and publishing packages with randomized names, which can lead to significant pollution of the npm registry.

Vulnerability Detail

The vulnerability in the man-nonatai-autgiag package stems from its malicious payload, which modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior not only compromises the integrity of the npm registry but also poses a risk to developers who may unknowingly install these malicious packages, potentially leading to further exploitation or data breaches.

How To Fix

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

npm uninstall man-nonatai-autgiag

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 prevent the installation of this package by using npm's package-lock.json to monitor dependencies. Ensure that your project does not include this package by regularly auditing your dependencies with 'npm audit'.

Conclusion

The man-nonatai-autgiag package poses a significant risk due to its malicious code designed to manipulate package metadata and publish unwanted variants. It is crucial for developers to be vigilant about their dependencies and utilize tools like Vulert to monitor for vulnerabilities. Immediate action should be taken to remove this package and prevent further exploitation.

See every vulnerability recorded for man-nonatai-autgiag →

Share this vulnerability

FAQ

The man-nonatai-autgiag package is an npm package that is part of a malicious campaign aimed at inflating developer reputation scores through automated package publishing.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time using just your package-lock.json file. Visit the Vulert playground at Vulert Scanner to check for vulnerabilities without needing to sign up.

The risks include the potential for installing malicious packages that can compromise your project's integrity and security, leading to data breaches or further exploitation.

Yes, regularly audit your dependencies using 'npm audit' and ensure that your package-lock.json does not include the man-nonatai-autgiag package.

If you have installed the man-nonatai-autgiag package, you should uninstall it immediately using 'npm uninstall man-nonatai-autgiag' and check for any other affected packages.

How To Fix

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

npm uninstall man-nonatai-autgiag

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