Malicious Code Injection in kuinsu-uiu-vilkukbimi Package

kuinsu-uiu-vilkukbimi Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-157802: Malicious code in kuinsu-uiu-vilkukbimi (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 kuinsu-uiu-vilkukbimi package is part of the npm ecosystem, primarily used for JavaScript applications. It is often involved in token reward campaigns, which can lead to the proliferation of malicious packages. This specific package has been identified as part of a scheme that generates and publishes numerous derivative packages to manipulate developer reputation scores.

Vulnerability Detail

The vulnerability in kuinsu-uiu-vilkukbimi stems from its association with the tea.xyz token reward campaign. It contains malicious scripts that modify the package.json file to remove private flags, alter version numbers, and create random package names. This behavior leads to the continuous republishing of variants, polluting the npm registry and potentially compromising the integrity of applications that depend on this package.

How To Fix

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

npm uninstall kuinsu-uiu-vilkukbimi

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 avoid using the kuinsu-uiu-vilkukbimi package altogether. If it is already in use, consider replacing it with a similar, trusted package that does not exhibit malicious behavior. You can also use the following command to uninstall it: npm uninstall kuinsu-uiu-vilkukbimi.

Conclusion

The kuinsu-uiu-vilkukbimi package poses a significant security risk due to its malicious code that alters package metadata and floods the npm registry. It is essential to remove this package and monitor your applications for vulnerabilities to maintain security.

See every vulnerability recorded for kuinsu-uiu-vilkukbimi →

Share this vulnerability

FAQ

kuinsu-uiu-vilkukbimi is an npm package associated with JavaScript applications, often linked to token reward campaigns.

The vulnerability can lead to the injection of malicious code, potentially compromising your application's integrity and security.

You should uninstall the kuinsu-uiu-vilkukbimi package immediately and monitor your application for any unusual behavior.

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

You can use the Vulert playground at Vulert Scanner to check if your application is affected without needing to sign up.

How To Fix

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

npm uninstall kuinsu-uiu-vilkukbimi

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