Malicious Code Injection in uinsu-losit-bisaua: A Threat to npm Ecosystem
Summary
MAL-2025-169900: Malicious code in uinsu-losit-bisaua (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-bisaua' is part of the npm ecosystem, which is widely used for JavaScript package management. This package is associated with the tea.xyz token reward campaign, which has been linked to a series of malicious activities aimed at inflating developer reputation scores. The package's functionality is compromised by the presence of malicious scripts that manipulate its metadata and behavior.
Vulnerability Detail
The vulnerability in 'uinsu-losit-bisaua' originates from its association with a malicious campaign that employs scripts to automatically generate and publish derivative packages. These scripts modify the package.json file by removing private flags, altering version numbers, and creating random package names. The continuous republishing of these variants leads to pollution of the npm registry, potentially affecting developers and users relying on legitimate packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall uinsu-losit-bisauaIf 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 remove the 'uinsu-losit-bisaua' package from your project by executing the command: 'npm uninstall uinsu-losit-bisaua'. This will prevent any malicious code from executing in your application until a secure version is available.
Conclusion
The 'uinsu-losit-bisaua' package is compromised by malicious code that poses a significant threat to the npm ecosystem. It is crucial for developers to take immediate action by updating or uninstalling the package to safeguard their applications. Utilizing tools like Vulert can enhance your security posture by providing real-time alerts for open-source vulnerabilities.
See every vulnerability recorded for uinsu-losit-bisaua →
FAQ
The vulnerability involves malicious code that modifies package metadata and repackages it under random names, affecting the integrity of the npm registry.
You can use Vulert to monitor and alert for open-source vulnerabilities in your software. Visit the Vulert playground at Vulert Scanner to check if your application is affected without any signup.
If an immediate update is not possible, consider uninstalling the package as a temporary measure to mitigate risks associated with the vulnerability.
While specific exploits have not been detailed, the nature of the vulnerability suggests that it could lead to the distribution of malicious packages, affecting users and developers.
Regularly audit your dependencies, use tools like Vulert for real-time monitoring, and stay informed about vulnerabilities in the npm ecosystem.
