Malicious Code Injection in kuinsu-lukoki-ntabi: A Threat to npm Users

kuinsu-lukoki-ntabi Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-157798: Malicious code in kuinsu-lukoki-ntabi (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

kuinsu-lukoki-ntabi is an npm package that is part of a larger ecosystem of packages associated with the tea.xyz token reward campaign. These packages are designed to manipulate npm's publishing system by creating derivative packages with randomized names, which can inflate developer reputation scores. This behavior poses a significant risk to the integrity of the npm registry and the security of applications relying on these packages.

Vulnerability Detail

The vulnerability in kuinsu-lukoki-ntabi stems from its inclusion in a malicious campaign that modifies the package.json file to remove private flags and change version numbers. It generates random package names, often themed around Indonesian culture, and continuously republishes these variants to pollute the npm registry. This can lead to security risks for developers who may unknowingly install these compromised packages, potentially exposing their applications to further vulnerabilities and malicious code.

How To Fix

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

npm uninstall kuinsu-lukoki-ntabi

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, avoid using the kuinsu-lukoki-ntabi package and consider using alternative packages that provide similar functionality without the associated risks. Regularly audit your dependencies using tools like Vulert, which monitors your package-lock.json for vulnerabilities in real-time.

Conclusion

The kuinsu-lukoki-ntabi package poses a significant security risk due to its malicious behavior of modifying package metadata and republishing compromised versions. It is essential for developers to remove this package and monitor their dependencies for vulnerabilities to maintain the security of their applications.

See every vulnerability recorded for kuinsu-lukoki-ntabi →

Share this vulnerability

FAQ

kuinsu-lukoki-ntabi is an npm package that is part of a malicious campaign aimed at manipulating the npm registry.

The vulnerability can lead to the installation of malicious code, compromising the security and integrity of your application.

You should uninstall the kuinsu-lukoki-ntabi package immediately and check for any other compromised packages in your project.

You can use 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 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 kuinsu-lukoki-ntabi

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