Malicious Code Injection in uinsu-lost-diunsvuta Package
Summary
MAL-2025-169950: Malicious code in uinsu-lost-diunsvuta (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-lost-diunsvuta package is part of a series of npm packages that emerged during the tea.xyz token reward campaign. These packages are designed to automate the generation and publication of derivative packages with randomized names, primarily to inflate developer reputation scores for token rewards. The malicious nature of this package lies in its ability to alter package.json files, removing private flags and modifying version numbers, which can lead to significant security risks and registry pollution.
Vulnerability Detail
The vulnerability in the uinsu-lost-diunsvuta package originates from its malicious intent to manipulate the npm registry. It includes scripts that automatically generate and publish numerous derivative packages with random names, effectively polluting the registry. This not only compromises the integrity of the npm ecosystem but also poses risks to developers who may unknowingly install these malicious packages, leading to potential data breaches or system compromises.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall uinsu-lost-diunsvutaIf 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-lost-diunsvuta package and any other packages that are part of the tea.xyz token reward campaign. Regularly audit your package.json and package-lock.json files to identify and remove any suspicious packages.
Conclusion
The uinsu-lost-diunsvuta package poses a significant security risk due to its malicious code designed to manipulate the npm registry. It is crucial for developers to be vigilant, regularly audit their dependencies, and utilize tools like Vulert to monitor for vulnerabilities. Immediate action should be taken to remove any affected packages to maintain the integrity of your projects.
See every vulnerability recorded for uinsu-lost-diunsvuta →
FAQ
The uinsu-lost-diunsvuta package is an npm package that is part of a malicious campaign aimed at inflating developer reputation scores through the automatic generation of derivative packages.
This vulnerability can lead to the pollution of the npm registry and may compromise your project's security if malicious packages are inadvertently installed.
If you have installed the uinsu-lost-diunsvuta package, you should uninstall it immediately using 'npm uninstall uinsu-lost-diunsvuta' and review your other dependencies for similar vulnerabilities.
You can use tools like Vulert, which monitors your package-lock.json for open-source vulnerabilities in real-time. You can check your application for vulnerabilities using the Vulert playground without any signup.
Yes, tools like Vulert can help you monitor and alert for open-source vulnerabilities in your software, ensuring you are aware of any potential risks.
