Malicious Code Injection in inufgi-goa-jamufi: A Threat to npm Ecosystem
Summary
MAL-2025-156609: Malicious code in inufgi-goa-jamufi (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-jamufi' is part of a series of malicious packages that emerged during the tea.xyz token reward campaign. These packages are designed to manipulate the npm registry by generating and publishing numerous derivative packages with altered names and metadata. The primary function of these packages is to inflate developer reputation scores for token rewards, posing a significant risk to the integrity of the npm ecosystem.
Vulnerability Detail
The vulnerability in 'inufgi-goa-jamufi' stems from its malicious payload, which modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior leads to the continuous republishing of variants, effectively polluting the npm registry. The origin of this vulnerability is linked to the exploitation of npm's publishing mechanisms, which can be manipulated to create a flood of low-quality or harmful packages, undermining trust in the ecosystem.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall inufgi-goa-jamufiIf 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 measure, you can avoid using the affected package by removing it from your dependencies. If you need similar functionality, consider using alternative packages that are well-reviewed and maintained. Always verify the integrity of packages before installation.
Conclusion
The 'inufgi-goa-jamufi' package represents a significant threat to the npm ecosystem due to its malicious behavior. It is essential for developers to remain vigilant, regularly audit their dependencies, and utilize tools like Vulert to monitor for vulnerabilities. By taking proactive measures, developers can help maintain the integrity of their projects and the broader open-source community.
See every vulnerability recorded for inufgi-goa-jamufi →
FAQ
The vulnerability can lead to the proliferation of malicious packages in the npm registry, compromising the integrity of the ecosystem and potentially affecting other projects that depend on these packages.
You can use tools like Vulert, which monitors your package-lock.json for vulnerabilities in real-time. You can also check your application against the Vulert playground without needing to sign up.
Immediately uninstall the package using 'npm uninstall inufgi-goa-jamufi' and review your dependencies for any other potentially harmful packages.
Yes, consider using well-established packages that provide similar functionality but have a proven track record and community support.
Regularly audit your dependencies, use tools like Vulert for monitoring, and only install packages from trusted sources.
