Malicious Code Injection in inufgi-gotuma-anz Package: A Threat to npm Ecosystem

inufgi-gotuma-anz Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-156696: Malicious code in inufgi-gotuma-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 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 inufgi-gotuma-anz package is part of a broader campaign targeting the npm ecosystem, designed to exploit developer reputation systems through the creation of numerous derivative packages. This package, like others in the campaign, is characterized by its ability to automatically generate and publish variants with randomized names, thus inflating scores for token rewards in the tea.xyz protocol. Its functionality is compromised due to the presence of malicious scripts that manipulate package metadata.

Vulnerability Detail

The vulnerability originates from the malicious code embedded within the inufgi-gotuma-anz package. This code modifies the package.json file to remove private flags, alters version numbers, and generates random package names, contributing to the pollution of the npm registry. The ramifications include potential security risks for developers who unknowingly integrate these compromised packages into their projects, leading to reputational damage and loss 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-gotuma-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 avoid using the inufgi-gotuma-anz package and any other packages that may have been published as part of the same campaign. Regularly audit your package dependencies using tools like Vulert to ensure your application remains secure.

Conclusion

The inufgi-gotuma-anz package poses a significant threat to the npm ecosystem due to its malicious code designed to manipulate package metadata and inflate developer reputation scores. It is crucial for developers to remove this package and monitor their dependencies to maintain the security and integrity of their projects.

See every vulnerability recorded for inufgi-gotuma-anz →

Share this vulnerability

FAQ

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

Integrating this package can lead to security risks and potential pollution of your project's dependency tree, affecting the overall integrity of your application.

You should uninstall the inufgi-gotuma-anz package immediately and monitor your dependencies for any other malicious packages.

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

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 inufgi-gotuma-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