Malicious Code Injection in inagi-vumafe-nabfufas Package
Summary
MAL-2025-156353: Malicious code in inagi-vumafe-nabfufas (npm). Affected versions are not published. No fix is published. How to fix ↓
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.
No signup required · Results in about 60 seconds
Background
The inagi-vumafe-nabfufas 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 aimed at exploiting npm's publishing capabilities. It is designed to generate and publish derivative packages with randomized names, which can lead to reputation inflation for malicious actors within the npm registry.
Vulnerability Detail
The vulnerability originates from the inagi-vumafe-nabfufas package, which contains scripts that automatically modify the package.json file to remove private flags and change version numbers. This allows the package to continuously republish variants with random names, polluting the npm registry and potentially compromising the integrity of other packages. The malicious payload can lead to unintended consequences for developers who may unknowingly use these compromised packages, resulting in security risks and loss of trust in the npm ecosystem.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall inagi-vumafe-nabfufasIf 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
Currently, the best workaround is to avoid using the inagi-vumafe-nabfufas package altogether. If it is already in use, uninstall it immediately and monitor your project for any unexpected behavior or dependencies that may have been affected.
Conclusion
The inagi-vumafe-nabfufas package poses a significant risk due to its malicious code that modifies package metadata and republish variants to the npm registry. It is crucial for developers to remove this package from their projects and monitor for any potential impacts. Utilizing tools like Vulert can help in identifying and managing such vulnerabilities effectively.
See every vulnerability recorded for inagi-vumafe-nabfufas →
FAQ
It is an npm package that has been identified as part of a malicious campaign to inflate developer reputation scores through the automatic generation of derivative packages.
Using the inagi-vumafe-nabfufas package can lead to the introduction of malicious code into your project, potentially compromising its security and integrity.
You should uninstall the package immediately and check your project for any unintended consequences or dependencies that may have been affected.
Yes, you can use Vulert to monitor your project for open-source vulnerabilities in real-time. It analyzes your package-lock.json file without requiring code access or installation.
You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.
