Malicious Code Injection in uagifa-afaoti-uto: A Threat to npm Packages
Summary
MAL-2025-169472: Malicious code in uagifa-afaoti-uto (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 'uagifa-afaoti-uto' is part of a series of npm packages that have been linked to a token reward campaign by tea.xyz. These packages are designed to manipulate the npm registry by automatically generating and publishing derivative packages with randomized names. This behavior is intended to inflate developer reputation scores for rewards associated with the tea protocol, making it a significant concern for developers relying on npm for package management.
Vulnerability Detail
The vulnerability in 'uagifa-afaoti-uto' originates from its malicious intent to modify the package.json file by removing private flags, altering version numbers, and generating random package names. This results in a pollution of the npm registry, making it difficult for developers to trust the integrity of packages. The malicious payload can lead to unauthorized access and manipulation of project dependencies, potentially compromising the security of applications that utilize these packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall uagifa-afaoti-utoIf 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 'uagifa-afaoti-uto' package and instead look for alternative packages that provide similar functionality without the associated risks. Additionally, consider implementing stricter controls on package installations and regularly auditing your package-lock.json file for vulnerabilities.
Conclusion
The 'uagifa-afaoti-uto' package poses a significant risk due to its malicious code that alters package.json files and pollutes the npm registry. Developers should take immediate action to remove this package and monitor their projects for vulnerabilities. Utilizing tools like Vulert can help maintain the integrity of your software dependencies.
See every vulnerability recorded for uagifa-afaoti-uto →
FAQ
The main threat is the malicious modification of package.json files, which can lead to unauthorized access and manipulation of project dependencies.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. You can check your application using the Vulert playground at Vulert Scanner without any signup.
Immediately uninstall the package using 'npm uninstall uagifa-afaoti-uto' and review your dependencies for any potential security risks.
Yes, you should look for reputable packages that offer similar functionality without the malicious behavior associated with uagifa-afaoti-uto.
Regularly audit your dependencies, use tools like Vulert for monitoring vulnerabilities, and ensure you only install packages from trusted sources.
