Malicious Code Injection in uinsu-lost-duu Package

uinsu-lost-duu Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-169955: Malicious code in uinsu-lost-duu (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-duu package is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to facilitate the automatic generation and publication of derivative packages, which can inflate developer reputation scores for token rewards. However, it has been identified as containing malicious code that compromises the integrity of the npm registry.

Vulnerability Detail

The vulnerability in the uinsu-lost-duu package originates from its malicious design, which includes scripts that modify the package.json file to remove private flags, alter version numbers, and generate random package names. This behavior leads to the continuous republishing of variants, polluting the npm registry and potentially affecting other developers by inflating reputation scores fraudulently. The malicious payload can also expose users to security risks by allowing unauthorized access to sensitive information.

How To Fix

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

npm uninstall uinsu-lost-duu

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-duu package altogether and look for alternative packages that provide similar functionality without the associated risks. Additionally, regularly audit your dependencies using tools like npm audit to identify and address vulnerabilities.

Conclusion

The uinsu-lost-duu package poses a significant security risk due to its malicious code that modifies package metadata and floods the npm registry. It is crucial to remove this package from your projects and monitor your dependencies for vulnerabilities to maintain the integrity of your software.

See every vulnerability recorded for uinsu-lost-duu →

Share this vulnerability

FAQ

The uinsu-lost-duu package is an npm package linked to the tea.xyz token reward campaign, designed to generate and publish derivative packages.

This vulnerability can lead to the pollution of the npm registry and may expose your project to security risks, including unauthorized access to sensitive information.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check if your application is affected without requiring any signup.

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

Yes, you can look for alternative npm packages that provide similar functionality without the associated risks. Always ensure to audit your dependencies.

How To Fix

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

npm uninstall uinsu-lost-duu

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