Malicious Code Injection in nokire-kilua60: A Threat to npm Ecosystem

nokire-kilua60 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-162652: Malicious code in nokire-kilua60 (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 package 'nokire-kilua60' is part of the npm ecosystem, which is widely used for JavaScript package management. It is designed to facilitate the development and sharing of code among developers. However, this package has been identified as part of a malicious campaign that aims to exploit the npm registry by generating and publishing derivative packages with randomized names, thereby inflating developer reputation scores for token rewards.

Vulnerability Detail

The vulnerability in 'nokire-kilua60' originates from its association with the tea.xyz token reward campaign. The malicious code embedded in this package modifies the package.json file by removing private flags, altering version numbers, and generating random package names. This results in the continuous republishing of variants that pollute the npm registry, potentially leading to security risks for developers who unknowingly use these compromised packages.

How To Fix

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

npm uninstall nokire-kilua60

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 'nokire-kilua60' package and instead look for alternative packages that provide similar functionality without the associated risks. Additionally, you can monitor your project for any unauthorized changes to your package.json file.

Conclusion

The 'nokire-kilua60' package poses a significant threat to the npm ecosystem due to its malicious code designed to manipulate package metadata and inflate developer reputation scores. It is crucial for developers to remove this package and monitor their projects for any unauthorized changes. Utilizing tools like Vulert can aid in maintaining the security of your applications.

See every vulnerability recorded for nokire-kilua60 →

Share this vulnerability

FAQ

'nokire-kilua60' is an npm package that has been identified as part of a malicious campaign targeting the npm registry.

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

You should uninstall the package immediately and monitor your project for any changes made by the malicious code.

You can use tools like Vulert, which monitors your package-lock.json file for open-source vulnerabilities in real-time.

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 nokire-kilua60

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