Malicious Code Injection in uinsu-lisa-amiaba Package

uinsu-lisa-amiaba Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-169817: Malicious code in uinsu-lisa-amiaba (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-lisa-amiaba 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 its integrity and the npm registry.

Vulnerability Detail

The vulnerability originates from the malicious payload embedded within the uinsu-lisa-amiaba package. It modifies the package.json file by removing private flags, altering version numbers, and generating random package names. This behavior leads to the continuous republishing of variants, which pollutes the npm registry and can potentially harm developers and users relying on legitimate packages. The malicious scripts included (auto.js, autopublish.js, etc.) are designed to automate this process, making it difficult to detect and mitigate.

How To Fix

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

npm uninstall uinsu-lisa-amiaba

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 workaround, avoid using the uinsu-lisa-amiaba package and any other packages associated with the tea.xyz token reward campaign. Regularly audit your dependencies using tools like Vulert, which monitors your package-lock.json for vulnerabilities in real-time. You can also check if your application is affected by this vulnerability using the Vulert playground at https://vulert.com/scanner without any signup.

Conclusion

The uinsu-lisa-amiaba package poses a significant security risk due to its malicious code that modifies package metadata and floods the npm registry. It is crucial for developers to remove this package and utilize tools like Vulert to monitor for vulnerabilities in their projects.

See every vulnerability recorded for uinsu-lisa-amiaba →

Share this vulnerability

FAQ

The uinsu-lisa-amiaba package is an npm package that is part of a malicious campaign to inflate developer reputation scores through automated publishing of derivative packages.

The vulnerability can lead to the pollution of the npm registry, making it difficult to find legitimate packages and potentially compromising the security of your application.

You should uninstall the uinsu-lisa-amiaba package immediately using 'npm uninstall uinsu-lisa-amiaba' and audit your other dependencies for similar vulnerabilities.

While many packages in the npm registry are trustworthy, it is crucial to regularly audit your dependencies and stay informed about known vulnerabilities.

You can use tools like Vulert, which allows you to monitor your package-lock.json for vulnerabilities in real-time without requiring access to your code or installation.

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-lisa-amiaba

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