Malicious Code Injection in uinsu-losit-bika: A Threat to npm Ecosystem
Summary
MAL-2025-169897: Malicious code in uinsu-losit-bika (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-losit-bika' is part of a broader campaign targeting the npm registry, specifically designed to exploit the tea.xyz token reward system. This package, like others in its category, is intended to inflate developer reputation scores by automatically generating and publishing numerous derivative packages with randomized names. The malicious nature of this package compromises the integrity of the npm ecosystem by polluting the registry with potentially harmful variants.
Vulnerability Detail
The vulnerability in 'uinsu-losit-bika' originates from its association with the tea.xyz token reward campaign. It contains scripts that modify the package.json file to remove private flags, alter version numbers, and generate random package names. This behavior not only inflates developer reputation scores but also leads to the continuous republishing of these variants, which can clutter the npm registry and expose users to potential security risks. The malicious payload can compromise the integrity of applications relying on this package, making it a significant threat.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall uinsu-losit-bika
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 'uinsu-losit-bika' package altogether and look for alternative packages that provide similar functionality without the associated risks. Additionally, consider using tools like Vulert to monitor your dependencies for vulnerabilities.
Conclusion
The uinsu-losit-bika package poses a significant threat to the npm ecosystem due to its malicious code designed to exploit the tea.xyz token reward system. It is crucial for developers to remove this package from their projects and monitor their dependencies for vulnerabilities using tools like Vulert. By staying vigilant and proactive, developers can protect their applications from potential security risks.
See every vulnerability recorded for uinsu-losit-bika →
FAQ
The uinsu-losit-bika package contains malicious code that modifies package.json files and floods the npm registry with derivative packages.
You can use Vulert's playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.
You should uninstall the package immediately using 'npm uninstall uinsu-losit-bika' and monitor your project for any other vulnerabilities.
While specific alternatives depend on your use case, consider searching for reputable packages that offer similar functionality without the risk of malicious behavior.
Vulert uses your package-lock.json file to monitor and alert you in real-time for open-source vulnerabilities in your software, helping you maintain a secure application.