Malicious Code Injection in uinsu-losiat-duk Package

uinsu-losiat-duk Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-169881: Malicious code in uinsu-losiat-duk (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 Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

Background

The uinsu-losiat-duk package is part of the npm ecosystem and appears to be associated with the tea.xyz token reward campaign. This package is designed to facilitate automatic publishing of derivative packages, which can inflate developer reputation scores for token rewards. However, it has been compromised to include malicious scripts that manipulate package metadata.

Vulnerability Detail

The vulnerability originates from the malicious code embedded within the uinsu-losiat-duk package. This code modifies the package.json file by removing private flags, altering version numbers, and generating random package names. The intent is to continuously republish these variants to pollute the npm registry, which can lead to significant reputational damage for developers and potential security risks for users who inadvertently install these compromised packages.

How To Fix

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

npm uninstall uinsu-losiat-duk

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, avoid using the uinsu-losiat-duk package and consider using alternative packages that provide similar functionality without the associated risks. Additionally, you can monitor your project for vulnerabilities using tools like Vulert, which analyzes your package-lock.json file for real-time alerts on open-source vulnerabilities.

Conclusion

The uinsu-losiat-duk package has been identified as containing malicious code that poses significant risks to developers and users. It is crucial to uninstall this package and monitor your projects for vulnerabilities using tools like Vulert. Staying informed and proactive can help mitigate the risks associated with compromised packages.

See every vulnerability recorded for uinsu-losiat-duk →

Share this vulnerability

FAQ

The uinsu-losiat-duk package is an npm package associated with a token reward campaign that automates the publishing of derivative packages.

The malicious code can modify your package.json file, leading to potential security risks and reputational damage by polluting the npm registry.

You should uninstall the uinsu-losiat-duk package immediately using 'npm uninstall uinsu-losiat-duk' and monitor your project for any vulnerabilities.

Yes, you can use Vulert to monitor your project for vulnerabilities by analyzing your package-lock.json file. It provides real-time alerts without requiring code access.

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

Sponsored Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

How To Fix

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

npm uninstall uinsu-losiat-duk

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