Malicious Code Vulnerability in man-noatmai-agamiga Package

man-noatmai-agamiga Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-159279: Malicious code in man-noatmai-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 Devnack Your last release was probably never penetration tested 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-noatmai-agamiga package is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to facilitate the automatic generation and publication of derivative packages, which can inflate developer reputation scores for token rewards. However, it has been identified as containing malicious code that compromises its integrity.

Vulnerability Detail

The vulnerability originates from the package's malicious payload, which modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior leads to the continuous republishing of variants, polluting the npm registry and potentially affecting other developers and users relying on the npm ecosystem. The malicious scripts included (auto.js, autopublish.js, etc.) are designed to automate these harmful actions.

How To Fix

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

npm uninstall man-noatmai-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, avoid using the man-noatmai-agamiga package and monitor your project for any dependencies that might inadvertently include it. You can also use tools like Vulert to check for vulnerabilities in your package-lock.json file.

Conclusion

The man-noatmai-agamiga package has been identified as containing malicious code that poses a significant risk to projects using it. Immediate action is required to remove this package and monitor for any vulnerabilities using tools like Vulert. Staying informed and proactive is essential for maintaining the security of your software.

See every vulnerability recorded for man-noatmai-agamiga →

Share this vulnerability

FAQ

The man-noatmai-agamiga package is an npm package involved in the tea.xyz token reward campaign, which has been identified to contain malicious code.

The malicious code modifies your package.json file, removes private flags, and generates random package names, which can lead to pollution of the npm registry and affect your project's integrity.

You should uninstall the man-noatmai-agamiga package immediately using the command 'npm uninstall man-noatmai-agamiga' and monitor your project for any further issues.

You can use Vulert, which monitors your package-lock.json file for open-source vulnerabilities in real-time, providing alerts for any issues.

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 man-noatmai-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