Malicious Code Injection in inagi-vumafe-nau Package

inagi-vumafe-nau Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-156361: Malicious code in inagi-vumafe-nau (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-vumafe-nau package is part of the npm ecosystem, which is widely used for JavaScript package management. This package has been identified as part of a malicious campaign that aims to exploit npm's publishing mechanisms. It is designed to automatically generate and publish derivative packages, which can lead to reputation inflation for the perpetrators and pollution of the npm registry.

Vulnerability Detail

The vulnerability in the inagi-vumafe-nau package stems from its association with a malicious campaign that modifies the package.json file to remove private flags and changes version numbers. This allows the package to generate random names and continuously republish variants, which can lead to a cluttered npm registry and potential security risks for developers who unknowingly use these packages. The malicious payload can compromise the integrity of applications relying on this package, leading to further exploitation.

How To Fix

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

npm uninstall inagi-vumafe-nau

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 workaround, you can avoid using the inagi-vumafe-nau package altogether. If it is already in use, consider removing it from your package.json file and running npm install to clean up your dependencies.

Conclusion

The inagi-vumafe-nau package poses a significant risk due to its malicious code injection capabilities. It is essential for developers to be aware of this vulnerability and take appropriate actions to secure their applications. Regular monitoring and updating of dependencies can help mitigate such risks.

See every vulnerability recorded for inagi-vumafe-nau →

Share this vulnerability

FAQ

The inagi-vumafe-nau package is an npm package that has been identified as part of a malicious campaign targeting the npm registry.

This vulnerability can lead to the injection of malicious code into your application, potentially compromising its security and integrity.

If you have installed the inagi-vumafe-nau package, it is crucial to remove it immediately and check for any potential impacts on your application.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software by analyzing your package-lock.json file.

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

How To Fix

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

npm uninstall inagi-vumafe-nau

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