Malicious Code Injection in inufgi-goa-jana: A Threat to npm Packages
Summary
MAL-2025-156613: Malicious code in inufgi-goa-jana (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 package 'inufgi-goa-jana' is part of the npm ecosystem, which is widely used for JavaScript package management. This package appears to be associated with a token reward campaign that has led to the proliferation of malicious packages on npm. Its functionality is compromised, as it is designed to manipulate package metadata and publish variants that can harm developers' reputations and the integrity of the npm registry.
Vulnerability Detail
The vulnerability in 'inufgi-goa-jana' stems from its malicious code that modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior is intended to inflate developer reputation scores through the automatic generation and publication of derivative packages. The malicious payload can lead to the pollution of the npm registry, making it difficult for developers to trust legitimate packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall inufgi-goa-janaIf 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-goa-jana' package and look for alternative packages that provide similar functionality without the associated risks. Additionally, you can use the following command to uninstall the package: npm uninstall inufgi-goa-jana.
Conclusion
The 'inufgi-goa-jana' package poses a significant risk due to its malicious code that manipulates package metadata and floods the npm registry with harmful variants. It is crucial for developers to remove this package and utilize tools like Vulert to monitor their projects for vulnerabilities. Staying informed and proactive can help maintain the integrity of your software.
See every vulnerability recorded for inufgi-goa-jana →
FAQ
The vulnerability involves malicious code that alters package metadata and publishes harmful variants to the npm registry.
You can check your project's dependencies using tools like Vulert, which monitors vulnerabilities in real-time based on your package-lock.json file.
It is advisable to uninstall the package immediately and monitor for any updates or patches that may be released.
Yes, regularly audit your dependencies, use tools like Vulert for monitoring vulnerabilities, and only install packages from trusted sources.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring an account.
