Malicious Code Injection in inufgi-gotama-aana Package: A Threat to npm Users

inufgi-gotama-aana Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-156650: Malicious code in inufgi-gotama-aana (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

The inufgi-gotama-aana package is part of a series of malicious packages that emerged during the tea.xyz token reward campaign. Designed to inflate developer reputation scores, these packages often contain scripts that automatically publish derivative packages with randomized names. This behavior not only clutters the npm registry but also poses a significant risk to users who may unknowingly install these compromised packages.

Vulnerability Detail

The vulnerability in the inufgi-gotama-aana 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 is intended to pollute the npm registry and can lead to the installation of compromised packages by unsuspecting developers. The origin of this vulnerability is linked to the broader issue of malicious packages flooding the npm ecosystem, specifically targeting the tea protocol token rewards.

How To Fix

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

npm uninstall inufgi-gotama-aana

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 inufgi-gotama-aana package and monitor your dependencies for any malicious activity. You can also utilize tools like Vulert to check for vulnerabilities in your package-lock.json file without requiring installation. For real-time monitoring, visit the Vulert playground at https://vulert.com/scanner.

Conclusion

The inufgi-gotama-aana package represents a significant threat within the npm ecosystem due to its malicious behavior aimed at manipulating developer reputation scores. It is crucial for developers to remain vigilant, regularly audit their dependencies, and utilize tools like Vulert to safeguard their projects from such vulnerabilities.

See every vulnerability recorded for inufgi-gotama-aana →

Share this vulnerability

FAQ

It is a malicious npm package that is part of a campaign to inflate developer reputation scores by flooding the npm registry with compromised packages.

You can use Vulert to monitor your package-lock.json for vulnerabilities. Visit Vulert Scanner to check your application without signing up.

Using this package can lead to the installation of malicious code, which may compromise your application and its dependencies.

Regularly audit your dependencies, use tools like Vulert for monitoring, and avoid installing packages from untrusted sources.

Immediately uninstall the inufgi-gotama-aana package using npm uninstall inufgi-gotama-aana and check your project for any other compromised packages.

How To Fix

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

npm uninstall inufgi-gotama-aana

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