Malicious Code Injection in uinsnu-lkui-kgnuauanmi: A Threat to npm Ecosystem

uinsnu-lkui-kgnuauanmi Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-169706: Malicious code in uinsnu-lkui-kgnuauanmi (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 MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

The package uinsnu-lkui-kgnuauanmi is part of the npm ecosystem, which is widely used for JavaScript package management. This package is associated with the tea.xyz token reward campaign, which has been known to flood the npm registry with malicious packages. These packages often contain scripts designed to manipulate package metadata and inflate developer reputation scores, posing a significant risk to the integrity of the npm ecosystem.

Vulnerability Detail

The vulnerability in uinsnu-lkui-kgnuauanmi originates from its malicious payload that modifies the package.json file. It removes private flags, alters version numbers, and generates random package names, leading to the continuous republishing of these variants. This behavior not only pollutes the npm registry but also compromises the security and reliability of applications that depend on this package. The malicious code is part of a broader trend of automated scripts that exploit 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 uinsnu-lkui-kgnuauanmi

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 and look for alternative packages that provide similar functionality without the associated risks. Additionally, consider using tools like Vulert to monitor your package-lock.json for vulnerabilities.

Conclusion

The uinsnu-lkui-kgnuauanmi package poses a significant threat due to its malicious code that alters package metadata and floods the npm registry. It is essential to remove this package from your projects and utilize tools like Vulert for ongoing monitoring of vulnerabilities to ensure the security of your applications.

See every vulnerability recorded for uinsnu-lkui-kgnuauanmi →

Share this vulnerability

FAQ

uinsnu-lkui-kgnuauanmi is an npm package that has been identified as malicious, associated with the tea.xyz token reward campaign.

The vulnerability can lead to the automatic modification of your package.json file, potentially compromising your application's integrity and security.

You should uninstall the package immediately using npm uninstall uinsnu-lkui-kgnuauanmi and monitor your dependencies for any further vulnerabilities.

Yes, tools like Vulert can help monitor your package-lock.json for open-source vulnerabilities in real-time.

Yes, you can use the Vulert playground at Vulert Scanner to check for vulnerabilities in your application without any signup.

How To Fix

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

npm uninstall uinsnu-lkui-kgnuauanmi

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