Malicious Code Injection in uinsu-lost-dauvu Package - npm Vulnerability

uinsu-lost-dauvu Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-169937: Malicious code in uinsu-lost-dauvu (npm). Affected versions are not published. No fix is published. How to fix ↓

Free scan

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.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

The uinsu-lost-dauvu package is part of the npm ecosystem, which is widely used for JavaScript package management. This package has been identified as part of a malicious campaign that aims to exploit the npm registry by flooding it with derivative packages. These packages are designed to inflate developer reputation scores through automated publishing scripts, which can lead to significant pollution of the npm registry and compromise the integrity of the ecosystem.

Vulnerability Detail

The vulnerability in the uinsu-lost-dauvu package stems from its association with a malicious campaign that modifies the package.json file to remove private flags and change version numbers. It generates random package names and continuously republishes variants, which can lead to the proliferation of malicious packages in the npm registry. This poses a risk to developers who may unknowingly install these compromised packages, potentially leading to security breaches or data loss.

How To Fix

This package is malicious. Remove it and rotate any credentials it could have accessed.

npm uninstall uinsu-lost-dauvu

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-lost-dauvu package and any other packages that may be associated with the tea.xyz token reward campaign. Monitor your project for any unexpected behavior or dependencies that may arise from using compromised packages.

Conclusion

The uinsu-lost-dauvu package poses a significant risk due to its malicious nature and the potential for widespread impact on the npm ecosystem. It is crucial for developers to remain vigilant, regularly update their dependencies, and utilize tools like Vulert to monitor for vulnerabilities.

See every vulnerability recorded for uinsu-lost-dauvu →

Share this vulnerability

FAQ

The uinsu-lost-dauvu package is an npm package that has been identified as part of a malicious campaign to exploit the npm registry.

This vulnerability can lead to the installation of malicious code in your project, potentially compromising security and data integrity.

If you have installed the uinsu-lost-dauvu package, you should uninstall it immediately using 'npm uninstall uinsu-lost-dauvu'.

You can use tools like Vulert, which monitors your package-lock.json file for open-source vulnerabilities in real-time. You can check your application for vulnerabilities using the Vulert playground without any signup.

There are no patches available for the uinsu-lost-dauvu package, as it is recommended to remove it entirely from your project.

How To Fix

This package is malicious. Remove it and rotate any credentials it could have accessed.

npm uninstall uinsu-lost-dauvu

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 →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback