Malicious Code Injection in uinsu-lost-dauu Package: npm Vulnerability

uinsu-lost-dauu Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-169936: Malicious code in uinsu-lost-dauu (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 Devnack Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The uinsu-lost-dauu package is part of the npm ecosystem, often utilized in JavaScript projects for various functionalities. However, it has been identified as part of a malicious campaign that floods the npm registry with harmful packages. These packages are designed to manipulate developer reputation scores through automated publishing scripts, which can lead to significant security risks.

Vulnerability Detail

The vulnerability in the uinsu-lost-dauu package stems from its association with a malicious campaign that modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior not only compromises the integrity of the npm registry but also poses risks to developers who may unknowingly install these malicious packages, leading to potential data breaches and exploitation of their applications.

How To Fix

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

npm uninstall uinsu-lost-dauu

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-dauu package and look for alternative packages that provide similar functionality without the associated risks. Additionally, regularly monitor your package-lock.json file for any unauthorized changes.

Conclusion

The uinsu-lost-dauu package poses a significant security risk due to its malicious code designed to manipulate npm registry entries. It is essential to remove this package from your projects and monitor for any unauthorized changes. Utilizing tools like Vulert can help in maintaining the security of your applications.

See every vulnerability recorded for uinsu-lost-dauu →

Share this vulnerability

FAQ

The uinsu-lost-dauu package is an npm package that has been identified as part of a malicious campaign aimed at manipulating developer reputation scores.

This vulnerability can lead to unauthorized modifications in your project's dependencies, potentially exposing your application to security risks and data breaches.

If you have installed the uinsu-lost-dauu package, you should uninstall it immediately and check for any other dependencies that may be affected.

Yes, you can use tools like Vulert, which monitors your package-lock.json file for open-source vulnerabilities in real-time without requiring code access or installation.

You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.

How To Fix

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

npm uninstall uinsu-lost-dauu

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