Malicious Code Injection in uinsu-losit-dulau: A Threat to npm Packages
Summary
MAL-2025-169922: Malicious code in uinsu-losit-dulau (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-dulau' 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 known to flood the npm registry with malicious packages. These packages often contain scripts designed to manipulate package metadata and inflate developer reputation scores, posing significant risks to users and the integrity of the npm registry.
Vulnerability Detail
The vulnerability in 'uinsu-losit-dulau' originates from its malicious intent to modify the package.json file by removing private flags, altering version numbers, and generating random package names. This behavior is executed through autopublish scripts that continuously republish variants of the package, leading to pollution of the npm registry. The ramifications include potential exposure of sensitive data, unauthorized access to systems, and degradation of the npm ecosystem's reliability.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall uinsu-losit-dulauIf 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 prevent the installation of this malicious package by using npm's package-lock.json to monitor your dependencies. Ensure that your project does not include 'uinsu-losit-dulau' in its dependencies. You can also use the following command to audit your npm packages for vulnerabilities: 'npm audit'.
Conclusion
The uinsu-losit-dulau package poses a significant threat due to its malicious behavior of altering package metadata and republishing variants. It is essential to remove this package from your projects and utilize tools like Vulert to monitor for vulnerabilities in real-time. Staying vigilant and proactive in managing dependencies will help maintain the integrity of your applications.
See every vulnerability recorded for uinsu-losit-dulau →
FAQ
The primary risk is the modification of package metadata, which can lead to unauthorized access and pollution of the npm registry.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check your application without any signup.
You should uninstall the package immediately using 'npm uninstall uinsu-losit-dulau' and audit your other dependencies for vulnerabilities.
There are no patches available for the uinsu-losit-dulau package as it is inherently malicious. The best course of action is to remove it from your project.
Regularly audit your npm packages, keep your dependencies updated, and use tools like Vulert to monitor for vulnerabilities.
