Malicious Code Injection in inagi-vumayfe-naba Package

inagi-vumayfe-naba Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-156364: Malicious code in inagi-vumayfe-naba (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 inagi-vumayfe-naba package is part of the npm ecosystem and has been identified as a malicious package associated with the tea.xyz token reward campaign. This package is designed to manipulate the npm registry by creating and publishing derivative packages with randomized names, thereby inflating developer reputation scores for token rewards. Its functionality is compromised due to the presence of autopublish scripts that automate the generation of these malicious packages.

Vulnerability Detail

The vulnerability stems from the malicious code embedded within the inagi-vumayfe-naba package. This code modifies the package.json file to remove private flags, alters version numbers, and generates random package names, which leads to the continuous republishing of these 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 capabilities.

How To Fix

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

npm uninstall inagi-vumayfe-naba

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 inagi-vumayfe-naba package and monitor your package-lock.json file for any dependencies that may include it. You can also utilize tools like Vulert to check for vulnerabilities in your project without requiring code access or installation. To check if your application is affected by this vulnerability, visit the Vulert playground at https://vulert.com/scanner.

Conclusion

The inagi-vumayfe-naba package poses a significant risk due to its malicious code that alters package metadata and floods the npm registry with unwanted variants. It is crucial for developers to remove this package and monitor their projects for vulnerabilities to maintain a secure development environment.

See every vulnerability recorded for inagi-vumayfe-naba →

Share this vulnerability

FAQ

The inagi-vumayfe-naba package is a malicious npm package associated with the tea.xyz token reward campaign, designed to manipulate the npm registry.

This vulnerability can lead to the pollution of the npm registry and potential security risks for your project if the malicious package is included as a dependency.

If you have installed the inagi-vumayfe-naba package, you should uninstall it immediately using the command npm uninstall inagi-vumayfe-naba.

Yes, you can use Vulert to monitor and alert you in real-time for open-source vulnerabilities in your software by analyzing your package-lock.json file.

You can check if your application is affected by visiting the Vulert playground at Vulert Scanner, where you can analyze your project without any signup.

How To Fix

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

npm uninstall inagi-vumayfe-naba

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