Malicious Code Injection in uinsu-losit-bi Package: A Threat to npm Users
Summary
MAL-2025-169895: Malicious code in uinsu-losit-bi (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 uinsu-losit-bi package is part of a series of npm packages associated with the tea.xyz token reward campaign. These packages are designed to manipulate the npm registry by creating and publishing numerous derivative packages with randomized names. This behavior is intended to inflate developer reputation scores for token rewards, making the package a potential threat to the integrity of the npm ecosystem.
Vulnerability Detail
The vulnerability in the uinsu-losit-bi package stems from its malicious code, which modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This allows the package to continuously republish variants, polluting the npm registry and potentially leading to security risks for users who unknowingly install these compromised packages. The origin of this vulnerability is linked to the broader malicious activity surrounding the tea.xyz token reward campaign, which exploits npm's publishing mechanisms.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall uinsu-losit-biIf 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 uinsu-losit-bi package and any other packages associated with the tea.xyz token reward campaign. Monitor your package-lock.json file for any unauthorized changes and consider using tools like Vulert to keep track of vulnerabilities in your dependencies.
Conclusion
The uinsu-losit-bi package poses a significant threat due to its malicious code that manipulates the npm registry. It is crucial for developers to be vigilant and remove such packages from their projects to maintain the security and integrity of their applications. Utilizing tools like Vulert can help in monitoring and alerting for open-source vulnerabilities in real-time.
See every vulnerability recorded for uinsu-losit-bi →
FAQ
The uinsu-losit-bi package is an npm package involved in a malicious campaign that aims to inflate developer reputation scores through the creation of numerous derivative packages.
If your application uses the uinsu-losit-bi package, it may inadvertently publish unauthorized packages to the npm registry, compromising the integrity of your application and potentially exposing it to security risks.
You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring any signup.
You should immediately uninstall the uinsu-losit-bi package using the command npm uninstall uinsu-losit-bi and review your other dependencies for any similar vulnerabilities.
There is no patch for the uinsu-losit-bi package itself, as it is recommended to remove the package entirely from your project.
