Malicious Code Injection in uinsu-lis-amudakinbua: A Threat to npm Ecosystem
Summary
MAL-2025-169800: Malicious code in uinsu-lis-amudakinbua (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 'uinsu-lis-amudakinbua' is part of a series of malicious npm packages associated with the tea.xyz token reward campaign. 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 token rewards, posing a significant risk to the integrity of the npm ecosystem.
Vulnerability Detail
The vulnerability in 'uinsu-lis-amudakinbua' originates from its malicious payload, which modifies the package.json file to remove private flags and alters version numbers. It generates random package names, primarily themed around Indonesian culture, and continuously republishes these variants to pollute the npm registry. This can lead to compromised developer environments and a cluttered package ecosystem, making it difficult for developers to find legitimate packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall uinsu-lis-amudakinbua
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 temporary workaround, you can avoid using the affected package and look for alternative packages that provide similar functionality. Always verify the legitimacy of packages before adding them to your project.
Conclusion
The 'uinsu-lis-amudakinbua' package poses a significant threat due to its malicious behavior aimed at manipulating the npm ecosystem. It is crucial for developers to be vigilant, regularly update their dependencies, and utilize tools like Vulert to monitor for vulnerabilities. By taking proactive measures, developers can safeguard their projects against such threats.
See every vulnerability recorded for uinsu-lis-amudakinbua →
FAQ
The primary risk is the potential for malicious code execution and the pollution of the npm registry, which can compromise the integrity of your development environment.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software. Visit Vulert Scanner to check your application without any signup.
If you have installed the package, you should uninstall it immediately using 'npm uninstall uinsu-lis-amudakinbua' and review your project for any potential impacts.
While specific alternatives depend on the functionality you need, always look for well-reviewed and actively maintained packages in the npm registry.
Regularly audit your dependencies, use tools like Vulert for real-time monitoring, and ensure to read package documentation and reviews before installation.