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

nokire-kilua98 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-162693: Malicious code in nokire-kilua98 (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 Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The package 'nokire-kilua98' is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to manipulate npm's publishing system, generating numerous derivative packages with randomized names. Its primary function is to inflate developer reputation scores for token rewards, making it a potential vector for malicious activities.

Vulnerability Detail

The vulnerability in 'nokire-kilua98' stems from its malicious code that modifies the package.json file by removing private flags and altering version numbers. It generates random package names, often themed around Indonesian culture, and continuously republishes these variants to clutter the npm registry. This behavior can lead to the proliferation of untrustworthy packages, potentially compromising the integrity of applications that depend on npm.

How To Fix

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

npm uninstall nokire-kilua98

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, consider using a package manager that allows you to lock down your dependencies or monitor for vulnerabilities. You can also utilize Vulert, which monitors your package-lock.json for vulnerabilities in real-time. To check if your application is affected by this vulnerability, visit the Vulert playground at https://vulert.com/scanner without needing to sign up.

Conclusion

The 'nokire-kilua98' package poses a significant threat due to its malicious code that modifies package metadata and floods the npm registry with untrustworthy packages. It is crucial for developers to remove this package and monitor their dependencies to maintain application security.

See every vulnerability recorded for nokire-kilua98 →

Share this vulnerability

FAQ

'nokire-kilua98' is an npm package involved in a token reward campaign that generates and publishes numerous derivative packages.

The malicious code can lead to the installation of untrustworthy packages, potentially compromising your application's security and integrity.

You should uninstall the package immediately using 'npm uninstall nokire-kilua98' and check for any other affected packages.

Yes, you can use tools like Vulert, which monitors your package-lock.json for vulnerabilities in real-time.

Regularly update your dependencies, monitor for vulnerabilities, and utilize tools that provide alerts for any security issues.

How To Fix

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

npm uninstall nokire-kilua98

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