Malicious Code Injection in uinsu-lost-diunsavvuta Package

uinsu-lost-diunsavvuta Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-169946: Malicious code in uinsu-lost-diunsavvuta (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-diunsavvuta package is part of the npm ecosystem, often used in JavaScript projects. It is associated with the tea.xyz token reward campaign, which has been linked to various malicious activities. This package is designed to manipulate npm registry entries and inflate developer reputation scores through automated scripts.

Vulnerability Detail

The vulnerability in the uinsu-lost-diunsavvuta package stems from its inclusion in a campaign that deploys malicious scripts to modify package.json files. These scripts remove private flags, alter version numbers, and generate random package names, leading to pollution of the npm registry. This can result in developers unknowingly using compromised packages, which may introduce security risks into their applications.

How To Fix

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

npm uninstall uinsu-lost-diunsavvuta

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-diunsavvuta package and any other packages associated with the tea.xyz token reward campaign. Monitor your package dependencies closely and consider using tools like Vulert to identify vulnerabilities in your project.

Conclusion

The uinsu-lost-diunsavvuta package poses a significant threat due to its malicious code that alters package metadata. It is essential to remove this package from your projects and monitor your dependencies for vulnerabilities to maintain the security of your applications.

See every vulnerability recorded for uinsu-lost-diunsavvuta →

Share this vulnerability

FAQ

The uinsu-lost-diunsavvuta package is an npm package associated with a malicious campaign that modifies package metadata to inflate developer reputation scores.

This vulnerability can lead to the introduction of malicious code into your project, potentially compromising its security and integrity.

If you have installed the uinsu-lost-diunsavvuta package, you should uninstall it immediately and review your project for any other compromised dependencies.

You can use tools like Vulert, which monitors your package-lock.json file to alert you in real-time about open-source vulnerabilities in your software.

Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring any signup.

How To Fix

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

npm uninstall uinsu-lost-diunsavvuta

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