Malicious Code Injection in uinsu-lost-dauku: A Threat to npm Users

uinsu-lost-dauku Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-169931: Malicious code in uinsu-lost-dauku (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 Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The package 'uinsu-lost-dauku' is part of a series of malicious npm packages that emerged during the tea.xyz token reward campaign. These packages are designed to inflate developer reputation scores by automatically generating and publishing derivative packages with randomized names. The malicious nature of this package lies in its ability to modify critical files such as package.json, which can lead to significant security risks for developers and their applications.

Vulnerability Detail

The vulnerability in 'uinsu-lost-dauku' originates from its inclusion in a broader scheme to manipulate the npm registry. It contains scripts that automatically alter package.json files by removing private flags, changing version numbers, and generating random package names. This behavior not only pollutes the npm registry but also compromises the integrity of applications that depend on this package, potentially leading to unauthorized access or data breaches.

How To Fix

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

npm uninstall uinsu-lost-dauku

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 measure, you can avoid using the 'uinsu-lost-dauku' package and any other packages associated with the tea.xyz token reward campaign. Regularly audit your package.json and package-lock.json files for any suspicious entries.

Conclusion

The 'uinsu-lost-dauku' package poses a significant threat to npm users due to its malicious code that alters package files and inflates developer reputation scores. It is essential to remove this package and monitor your dependencies to maintain the security of your applications.

See every vulnerability recorded for uinsu-lost-dauku →

Share this vulnerability

FAQ

It is a malicious npm package that is part of a scheme to inflate developer reputation scores through automated publishing of derivative packages.

The vulnerability can lead to unauthorized modifications of your package.json file, potentially compromising your application's security and integrity.

You should uninstall the package immediately using 'npm uninstall uinsu-lost-dauku' and audit your project for any other malicious packages.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software using just package-lock.json. Visit Vulert Scanner to check if your application is affected without needing to sign up.

Yes, tools like Vulert can help you monitor your dependencies for vulnerabilities in real-time.

How To Fix

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

npm uninstall uinsu-lost-dauku

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