Malicious Code Injection in uinsu-lis-adakinu Package: A Threat to npm Ecosystem

uinsu-lis-adakinu Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-169797: Malicious code in uinsu-lis-adakinu (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 Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

The uinsu-lis-adakinu package is part of a larger campaign targeting the npm ecosystem, primarily associated with the tea.xyz token reward initiative. This package, like others in the campaign, is designed to manipulate the npm registry by generating and publishing numerous derivative packages with randomized names. Its functionality is compromised due to the malicious code embedded within, which alters package metadata and inflates developer reputation scores.

Vulnerability Detail

The vulnerability stems from the malicious code embedded in the uinsu-lis-adakinu package, which modifies the package.json file to remove private flags, changes version numbers, and generates random package names. This behavior leads to the continuous republishing of variants, polluting the npm registry and potentially compromising the integrity of other packages. The origin of this vulnerability is linked to a broader malicious campaign aimed at exploiting the npm ecosystem for token rewards.

How To Fix

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

npm uninstall uinsu-lis-adakinu

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, you can temporarily prevent the installation of the uinsu-lis-adakinu package by using npm's package-lock.json to monitor dependencies. Ensure that your project does not include this package in its dependencies list.

Conclusion

The uinsu-lis-adakinu package poses a significant threat to the npm ecosystem due to its malicious code that alters package metadata and inflates developer reputation scores. It is crucial for developers to remove this package and monitor their dependencies for vulnerabilities to maintain the integrity and security of their applications.

See every vulnerability recorded for uinsu-lis-adakinu →

Share this vulnerability

FAQ

The uinsu-lis-adakinu package is part of a malicious campaign that targets the npm ecosystem, designed to manipulate package metadata and inflate developer reputation scores.

The vulnerability can lead to the pollution of the npm registry, potentially compromising the integrity of your project's dependencies and affecting the overall security of your application.

You should remove the uinsu-lis-adakinu package from your project and monitor for any updates or patches that may be released.

You can use tools like Vulert, which monitors and alerts in real-time for open-source vulnerabilities using just your package-lock.json file.

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-lis-adakinu

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