Malicious Code Injection in kuinsu-uiu-vilumi: A Threat to npm Users

kuinsu-uiu-vilumi Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-157806: Malicious code in kuinsu-uiu-vilumi (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

kuinsu-uiu-vilumi is an npm package that is part of the tea.xyz token reward campaign. This package is designed to facilitate the distribution of token rewards through various npm packages. However, it has been identified as containing malicious code that can compromise the integrity of the npm registry and the applications that depend on it.

Vulnerability Detail

The vulnerability originates from a malicious payload embedded within the kuinsu-uiu-vilumi package. This payload modifies the package.json file to remove private flags, alters version numbers, and generates random package names, leading to the automatic publication of derivative packages. This behavior not only inflates developer reputation scores for the tea protocol but also pollutes the npm registry with potentially harmful packages. The ramifications include the risk of dependency confusion, where developers may inadvertently use compromised packages, leading to security breaches in their applications.

How To Fix

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

npm uninstall kuinsu-uiu-vilumi

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 workaround, you can remove the kuinsu-uiu-vilumi package from your project by executing the following command: npm uninstall kuinsu-uiu-vilumi. This will prevent any malicious code from executing until a secure version is available.

Conclusion

The kuinsu-uiu-vilumi package poses a significant risk due to its embedded malicious code, which can compromise the integrity of applications relying on it. It is essential to take immediate action by updating or removing the package and utilizing tools like Vulert to monitor for vulnerabilities in your projects.

See every vulnerability recorded for kuinsu-uiu-vilumi →

Share this vulnerability

FAQ

kuinsu-uiu-vilumi is an npm package associated with the tea.xyz token reward campaign, designed to facilitate token distribution.

The malicious code can modify your package.json file, leading to the publication of harmful derivative packages that may compromise your application's security.

You should uninstall the package immediately and monitor for any updates or patches that address the vulnerability.

You can use tools like Vulert, which monitors your package-lock.json file for open-source vulnerabilities in real-time without requiring code access or installation.

Yes, you can use the Vulert playground at Vulert Scanner 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 kuinsu-uiu-vilumi

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