Malicious Code Injection in kamasada-ntai-kyai Package

kamasada-ntai-kyai Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-157287: Malicious code in kamasada-ntai-kyai (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 kamasada-ntai-kyai package is part of the npm ecosystem, which is widely used for JavaScript development. This package, like many others, is intended to facilitate various functionalities within applications. However, it has been identified as part of a malicious campaign that seeks to exploit npm's publishing system, leading to potential security risks for developers and users alike.

Vulnerability Detail

The vulnerability in the kamasada-ntai-kyai package stems from its association with a malicious campaign that floods the npm registry with derivative packages. These packages contain scripts that automatically modify the package.json file to remove private flags, alter version numbers, and generate random package names. This behavior not only inflates developer reputation scores for token rewards but also pollutes the npm registry, making it difficult for developers to find legitimate packages. The malicious payload can lead to unauthorized access, data breaches, and a compromised development environment.

How To Fix

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

npm uninstall kamasada-ntai-kyai

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 kamasada-ntai-kyai package from your project by executing the following command: npm uninstall kamasada-ntai-kyai. This will prevent any malicious code from executing until a fix is applied.

Conclusion

The kamasada-ntai-kyai package poses a significant security risk due to its malicious code injection. Developers are advised to take immediate action by uninstalling the package and monitoring for updates. Utilizing tools like Vulert can help ensure your applications remain secure against such vulnerabilities.

See every vulnerability recorded for kamasada-ntai-kyai →

Share this vulnerability

FAQ

The kamasada-ntai-kyai package is an npm package that has been identified as part of a malicious campaign targeting the npm registry.

This vulnerability can lead to unauthorized modifications in your package.json file, potentially compromising your application's integrity and security.

If you have installed the kamasada-ntai-kyai package, it is crucial to uninstall it immediately and monitor for any updates or patches.

Yes, you can use Vulert, which monitors open-source vulnerabilities in your software. You can check your application using the Vulert playground without any signup at Vulert Scanner.

Long-term implications include potential data breaches, compromised application functionality, and damage to your reputation as a developer if your application is found to be using malicious packages.

How To Fix

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

npm uninstall kamasada-ntai-kyai

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