Malicious Code Injection in inufgi-gotumafa-anfufafaz: A Threat to npm Packages

inufgi-gotumafa-anfufafaz Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-156710: Malicious code in inufgi-gotumafa-anfufafaz (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 Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

Background

The package 'inufgi-gotumafa-anfufafaz' is part of a malicious campaign targeting the npm ecosystem, specifically linked to the tea.xyz token reward initiative. This package is designed to manipulate npm's package registry by generating and publishing numerous derivative packages with randomized names, thereby inflating developer reputation scores for token rewards. Its functionality is primarily centered around automating the publication process, which poses significant risks to the integrity of the npm registry.

Vulnerability Detail

The vulnerability originates from the malicious intent behind the package, which includes scripts that modify the package.json file to remove private flags and alter version numbers. This allows the package to continuously republish variants, polluting the npm registry with potentially harmful packages. The technical aspects involve the use of autopublish scripts that automate the creation of these derivative packages, making it difficult for developers to track and manage their dependencies effectively.

How To Fix

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

npm uninstall inufgi-gotumafa-anfufafaz

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 affected package by removing it from your dependencies. Additionally, consider using tools like Vulert to monitor your package-lock.json for vulnerabilities. You can check if your application is affected by this vulnerability using the Vulert playground at https://vulert.com/scanner without any signup.

Conclusion

The 'inufgi-gotumafa-anfufafaz' package poses a significant risk to the npm ecosystem due to its malicious code designed to manipulate package publishing. It is crucial for developers to remain vigilant, regularly audit their dependencies, and utilize tools like Vulert to ensure the security of their applications.

See every vulnerability recorded for inufgi-gotumafa-anfufafaz →

Share this vulnerability

FAQ

The main threat is the injection of malicious code that modifies package.json files and republish variants, which can lead to dependency confusion and security risks.

You can check your package.json and package-lock.json files for the presence of 'inufgi-gotumafa-anfufafaz'.

Remove the package from your dependencies and monitor your project for any updates or patches that address this vulnerability.

Yes, you can use tools like Vulert, which monitors your package-lock.json for open-source vulnerabilities in real-time.

Research alternative packages that are well-maintained and have a good reputation in the community to avoid similar vulnerabilities.

Sponsored Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

How To Fix

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

npm uninstall inufgi-gotumafa-anfufafaz

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