Malicious Code Injection in inufgi-gotumaa-anz: A Threat to npm Packages

inufgi-gotumaa-anz Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-156697: Malicious code in inufgi-gotumaa-anz (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 package 'inufgi-gotumaa-anz' is part of a series of npm packages that emerged during the tea.xyz token reward campaign. These packages are designed to manipulate the npm registry by generating and publishing numerous derivative packages with randomized names. This behavior is intended to inflate developer reputation scores for token rewards, making it a significant concern for the integrity of the npm ecosystem.

Vulnerability Detail

The vulnerability in 'inufgi-gotumaa-anz' originates from its malicious payload, which modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This results in continuous republishing of variants, effectively polluting the npm registry. The ramifications include potential security risks for developers who may unknowingly use these compromised packages, leading to further exploitation and degradation of trust in the npm ecosystem.

How To Fix

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

npm uninstall inufgi-gotumaa-anz

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 remove the 'inufgi-gotumaa-anz' package from your project by executing the command: 'npm uninstall inufgi-gotumaa-anz'. This will prevent any malicious code from executing until a patch is available.

Conclusion

The 'inufgi-gotumaa-anz' package poses a significant risk due to its malicious code designed to manipulate the npm registry. It is crucial for developers to be aware of such vulnerabilities, take immediate action to remove affected packages, and utilize monitoring tools like Vulert to safeguard their projects.

See every vulnerability recorded for inufgi-gotumaa-anz →

Share this vulnerability

FAQ

It is an npm package that is part of a malicious campaign to inflate developer reputation scores through the creation of numerous derivative packages.

The vulnerability can lead to the introduction of malicious code into your project, potentially compromising security and functionality.

You should uninstall the package immediately and monitor your project for any unusual behavior.

You can use tools like Vulert, which monitors your package-lock.json file for open-source vulnerabilities in real-time. You can check your application against known vulnerabilities using the Vulert playground.

Regularly updating your dependencies, using reliable package sources, and employing monitoring tools can help mitigate the risk of vulnerabilities.

How To Fix

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

npm uninstall inufgi-gotumaa-anz

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