Malicious Code Injection in nokire-kilua69: A Threat to npm Users

nokire-kilua69 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-162661: Malicious code in nokire-kilua69 (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 package 'nokire-kilua69' is part of a malicious campaign targeting npm users, specifically linked to the tea.xyz token reward initiative. This package is designed to manipulate the npm registry by creating and publishing numerous derivative packages with altered names and configurations. Its primary function is to inflate developer reputation scores for token rewards, making it a significant threat to the integrity of the npm ecosystem.

Vulnerability Detail

The vulnerability in 'nokire-kilua69' originates from its malicious intent to modify the package.json file by removing private flags and changing version numbers. It generates random package names, often themed around Indonesian culture, and continuously republishes these variants to clutter the npm registry. This behavior not only compromises the security of the affected packages but also undermines the trustworthiness of the npm ecosystem, potentially leading to further exploitation by malicious actors.

How To Fix

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

npm uninstall nokire-kilua69

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, you can avoid using the 'nokire-kilua69' package and monitor your project for any unauthorized changes. Regularly audit your package.json and package-lock.json files to ensure no malicious modifications have occurred.

Conclusion

The 'nokire-kilua69' package represents a significant threat to npm users due to its malicious behavior aimed at manipulating the npm registry. It is essential to remove this package and regularly monitor your dependencies for vulnerabilities to maintain the security and integrity of your projects.

See every vulnerability recorded for nokire-kilua69 →

Share this vulnerability

FAQ

'nokire-kilua69' is a malicious npm package that is part of a campaign to inflate developer reputation scores through the creation of numerous derivative packages.

The vulnerability can lead to unauthorized modifications in your project’s dependencies, potentially introducing security risks and instability.

You should uninstall the package immediately using 'npm uninstall nokire-kilua69' and audit your project for any other malicious packages.

Regularly audit your dependencies, use tools like Vulert to monitor for vulnerabilities, and avoid installing packages from untrusted sources.

Vulert is a tool that monitors and alerts for open-source vulnerabilities in your software using just the package-lock.json file. You can check for vulnerabilities in your application without any signup at the Vulert playground.

How To Fix

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

npm uninstall nokire-kilua69

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