Malicious Code Injection in uinsnu-lkui-kgnuabuanmi: npm Package Vulnerability

uinsnu-lkui-kgnuabuanmi Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-169704: Malicious code in uinsnu-lkui-kgnuabuanmi (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 package uinsnu-lkui-kgnuabuanmi 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 modifies package metadata and publishes harmful variants.

Vulnerability Detail

The vulnerability in uinsnu-lkui-kgnuabuanmi stems from its malicious payload, which alters the package.json file to remove private flags, changes version numbers, and generates random package names. This behavior leads to the pollution of the npm registry with numerous derivative packages, potentially compromising the integrity of the ecosystem and affecting developers' reputations.

How To Fix

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

npm uninstall uinsnu-lkui-kgnuabuanmi

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 avoid using the affected package by removing it from your dependencies and replacing it with a trusted alternative. Additionally, regularly audit your npm packages using 'npm audit' to identify and address vulnerabilities.

Conclusion

The uinsnu-lkui-kgnuabuanmi package poses a significant risk due to its malicious code that alters package metadata and floods the npm registry with harmful variants. It is crucial to remove this package from your project and monitor for any potential impacts. Utilizing tools like Vulert can help maintain the security of your open-source dependencies.

See every vulnerability recorded for uinsnu-lkui-kgnuabuanmi →

Share this vulnerability

FAQ

uinsnu-lkui-kgnuabuanmi is an npm package that has been identified as malicious, designed to inflate developer reputation scores through the automatic generation of derivative packages.

This vulnerability can lead to the pollution of the npm registry and may compromise the integrity of your project by introducing malicious packages.

You should uninstall the package immediately and monitor your project for any unusual behavior. Use 'npm uninstall uinsnu-lkui-kgnuabuanmi' to remove it.

You can use tools like Vulert, which monitors and alerts for open-source vulnerabilities in real-time using just your package-lock.json file. You can check your application on the Vulert playground without signing up.

Regularly audit your dependencies using 'npm audit' and consider using tools like Vulert to keep track of vulnerabilities in your open-source packages.

How To Fix

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

npm uninstall uinsnu-lkui-kgnuabuanmi

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