Malicious Code Injection in inagi-vumayfe-naya Package

inagi-vumayfe-naya Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-156370: Malicious code in inagi-vumayfe-naya (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 inagi-vumayfe-naya package is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to facilitate the automatic generation and publication of derivative packages, which can inflate developer reputation scores for token rewards. However, it has been identified as containing malicious code that compromises its integrity and the security of applications using it.

Vulnerability Detail

The vulnerability in the inagi-vumayfe-naya package stems from its inclusion in a malicious campaign that modifies the package.json file to remove private flags and changes version numbers. It generates random package names and continuously republishes variants, polluting the npm registry. This behavior can lead to unintended consequences for developers, including the risk of using compromised packages and potential exposure to further attacks.

How To Fix

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

npm uninstall inagi-vumayfe-naya

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 inagi-vumayfe-naya package and look for alternative packages that provide similar functionality without the associated risks. Additionally, you can monitor your project for vulnerabilities using tools like Vulert, which can alert you to open-source vulnerabilities in real-time.

Conclusion

The inagi-vumayfe-naya package poses a significant security risk due to its malicious code that modifies package files and repackages itself. It is essential to remove this package from your projects and monitor for vulnerabilities using tools like Vulert to ensure the security of your applications.

See every vulnerability recorded for inagi-vumayfe-naya →

Share this vulnerability

FAQ

It is an npm package associated with a token reward campaign that has been identified as containing malicious code.

The vulnerability can lead to the use of compromised packages, potentially exposing your application to security risks and attacks.

You should uninstall the inagi-vumayfe-naya package immediately and check for any references in your package-lock.json file.

Yes, you can use Vulert to monitor your project for open-source vulnerabilities in real-time without needing to access the code.

You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.

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 inagi-vumayfe-naya

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