Malicious Code Injection in kuinsu-uilu-vinalaiumai Package

kuinsu-uilu-vinalaiumai Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-157800: Malicious code in kuinsu-uilu-vinalaiumai (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-uilu-vinalaiumai package is part of the npm ecosystem, which is widely used for JavaScript package management. This package, like many others, is intended to facilitate development by providing reusable code. However, it has been identified as part of a malicious campaign that exploits npm's publishing mechanisms to inflate developer reputation scores through the creation of derivative packages.

Vulnerability Detail

The vulnerability originates from a malicious payload embedded within the kuinsu-uilu-vinalaiumai package. This payload modifies the package.json file to remove private flags, alters version numbers, and generates random package names, primarily themed around Indonesian culture. The malicious scripts continuously republish these variants to the npm registry, leading to pollution of the registry and potential security risks for developers who unknowingly use these packages.

How To Fix

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

npm uninstall kuinsu-uilu-vinalaiumai

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-uilu-vinalaiumai package until a secure version is released. Additionally, consider using alternative packages that provide similar functionality without the associated risks.

Conclusion

The kuinsu-uilu-vinalaiumai package has been identified as containing malicious code that can compromise the integrity of projects using it. It is essential to take immediate action by updating or removing the package to safeguard your application. Utilizing tools like Vulert can help in monitoring and identifying vulnerabilities in your dependencies.

See every vulnerability recorded for kuinsu-uilu-vinalaiumai →

Share this vulnerability

FAQ

It is an npm package used for JavaScript development, but it has been identified as part of a malicious campaign.

The vulnerability can lead to the introduction of malicious code into your project, potentially compromising security and functionality.

You should immediately update the package to the latest version or remove it from your project to prevent any security risks.

You can use tools like Vulert, which monitors your package-lock.json for 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 any signup.

How To Fix

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

npm uninstall kuinsu-uilu-vinalaiumai

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