Malicious Code Injection in uinsu-lisa-am Package: A Threat to npm Ecosystem

uinsu-lisa-am Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-169809: Malicious code in uinsu-lisa-am (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 Your last release was probably never penetration tested 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-lisa-am package is part of the npm ecosystem, which is widely used for JavaScript development. This package has been identified as part of a malicious campaign that aims to exploit the npm registry by flooding it with derivative packages. The primary functionality of uinsu-lisa-am is not well-defined due to its malicious nature, but it is involved in generating and publishing random package names to inflate developer reputation scores for token rewards.

Vulnerability Detail

The vulnerability in the uinsu-lisa-am package originates from its design to automatically modify the package.json file, removing private flags and changing version numbers. It generates random package names, often themed around Indonesian culture, and continuously republishes these variants to pollute the npm registry. This behavior can lead to significant ramifications, including the compromise of developer accounts, the proliferation of malicious packages, and potential security risks for applications relying on these packages.

How To Fix

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

npm uninstall uinsu-lisa-am

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 measure, you can prevent the installation of this malicious package by using npm's package-lock.json file to monitor dependencies. Ensure that your project does not include uinsu-lisa-am or any of its derivatives. You can also use tools like Vulert to monitor your project for vulnerabilities without requiring code access.

Conclusion

The uinsu-lisa-am package poses a significant threat to the npm ecosystem due to its malicious behavior of generating and publishing derivative packages. It is essential for developers to be vigilant, regularly update their dependencies, and utilize tools like Vulert to monitor for vulnerabilities. Immediate action is required to mitigate the risks associated with this package.

See every vulnerability recorded for uinsu-lisa-am →

Share this vulnerability

FAQ

The uinsu-lisa-am package is a malicious npm package designed to flood the npm registry with derivative packages for the purpose of inflating developer reputation scores.

This vulnerability can compromise your project by introducing malicious code, leading to potential security risks and the pollution of your project's dependency tree.

You should immediately uninstall the uinsu-lisa-am package using 'npm uninstall uinsu-lisa-am' and check your project for any other malicious dependencies.

Yes, regularly update your dependencies, use tools like Vulert to monitor vulnerabilities, and review your package-lock.json file for any suspicious packages.

Vulert is a service that monitors and alerts for open-source vulnerabilities in your software by analyzing your package-lock.json file. You can use the Vulert playground to check if your application is affected by this vulnerability without signing up.

How To Fix

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

npm uninstall uinsu-lisa-am

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