Malicious Code Injection in inufgi-gotma-anfzi Package: A Threat to npm Users

inufgi-gotma-anfzi Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-156676: Malicious code in inufgi-gotma-anfzi (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 Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The inufgi-gotma-anfzi package is part of the npm ecosystem and has been identified as a malicious package linked to the tea.xyz token reward campaign. This package is designed to manipulate the npm registry by generating and publishing derivative packages with randomized names, which can inflate developer reputation scores for token rewards. Its functionality is primarily centered around automating the publication of these packages, making it a significant threat to the integrity of the npm registry.

Vulnerability Detail

The vulnerability stems from the malicious code embedded within the inufgi-gotma-anfzi package. This code modifies the package.json file to remove private flags, alters version numbers, and generates random package names, leading to the continuous republishing of variants. The ramifications include pollution of the npm registry, potential security risks for developers using these packages, and a compromised reputation system within the npm ecosystem. The origin of this vulnerability is linked to the tea.xyz token reward campaign, which exploits npm's publishing mechanisms.

How To Fix

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

npm uninstall inufgi-gotma-anfzi

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-gotma-anfzi package and monitor your project for any dependencies that may indirectly include it. Regularly check your package-lock.json file for any unexpected packages and remove them if necessary.

Conclusion

The inufgi-gotma-anfzi package poses a significant threat to npm users due to its malicious code designed to manipulate the npm registry. It is essential to remove this package from your projects and monitor your dependencies to ensure the security and integrity of your applications.

See every vulnerability recorded for inufgi-gotma-anfzi →

Share this vulnerability

FAQ

The inufgi-gotma-anfzi package is a malicious npm package linked to a token reward campaign that automates the publication of derivative packages.

This vulnerability can lead to the pollution of the npm registry and may introduce security risks if your project inadvertently uses these malicious packages.

You should uninstall the inufgi-gotma-anfzi package immediately using the command: npm uninstall inufgi-gotma-anfzi.

You can use tools like Vulert, which monitors your package-lock.json file for open-source 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-gotma-anfzi

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