Malicious Code Injection in uinsu-lotsi-banl Package: npm Vulnerability Overview

uinsu-lotsi-banl Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-170055: Malicious code in uinsu-lotsi-banl (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-lotsi-banl package is part of a series of malicious packages that emerged during the tea.xyz token reward campaign on npm. These packages are designed to manipulate the npm registry by creating and publishing numerous derivative packages with randomized names, aimed at inflating developer reputation scores for token rewards. The package's functionality is compromised, making it a vector for malicious activities.

Vulnerability Detail

The vulnerability in the uinsu-lotsi-banl package stems from its malicious code, which modifies the package.json file to remove private flags and alters version numbers. It generates random package names, primarily themed around Indonesian culture, and continuously republishes these variants to pollute the npm registry. This behavior can lead to significant security risks, including the potential for dependency confusion and the exploitation of unsuspecting developers who may unknowingly install these compromised packages.

How To Fix

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

npm uninstall uinsu-lotsi-banl

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-lotsi-banl package altogether and look for alternative packages that provide similar functionality without the associated risks. Additionally, consider using tools like Vulert to monitor your project for vulnerabilities. You can check if your application is affected by this vulnerability using the Vulert playground at https://vulert.com/scanner without any signup.

Conclusion

The uinsu-lotsi-banl package presents a significant security threat due to its malicious code that alters package metadata and floods the npm registry with compromised packages. It is crucial for developers to remove this package and monitor their projects for vulnerabilities to maintain the integrity of their software.

See every vulnerability recorded for uinsu-lotsi-banl →

Share this vulnerability

FAQ

The uinsu-lotsi-banl package is a malicious npm package that is part of a campaign to inflate developer reputation scores through the creation of numerous derivative packages.

This vulnerability can lead to dependency confusion, where your project may inadvertently use compromised packages, exposing it to security risks.

You should uninstall the uinsu-lotsi-banl package immediately using 'npm uninstall uinsu-lotsi-banl' and check for any other affected packages in your project.

Yes, you can use Vulert, which monitors and alerts you in real-time for open-source vulnerabilities in your software by analyzing your package-lock.json file.

Absolutely! You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.

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-lotsi-banl

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