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

nokire-kilua433 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-162633: Malicious code in nokire-kilua433 (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

The package 'nokire-kilua433' is part of the npm ecosystem, which is widely used for managing JavaScript packages. This package is associated with the tea.xyz token reward campaign, which has been known to flood the npm registry with malicious packages. These packages often contain scripts designed to manipulate package metadata and inflate developer reputation scores, posing significant risks to users and the integrity of the npm registry.

Vulnerability Detail

The vulnerability in 'nokire-kilua433' stems from its malicious code that modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior is part of a broader scheme to publish derivative packages that pollute the npm registry, potentially leading to reputational damage for developers and security risks for users who inadvertently install these packages. The origin of this vulnerability is linked to the tea.xyz token reward campaign, which exploits npm's package management system.

How To Fix

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

npm uninstall nokire-kilua433

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 'nokire-kilua433' and any other packages associated with the tea.xyz token reward campaign. Regularly audit your project's dependencies to identify and remove any potentially malicious packages.

Conclusion

The 'nokire-kilua433' package poses a significant threat due to its malicious code designed to manipulate npm package metadata. It is essential for developers to remove this package from their projects and to remain vigilant about the packages they use. Utilizing tools like Vulert can help monitor for such vulnerabilities effectively.

See every vulnerability recorded for nokire-kilua433 →

Share this vulnerability

FAQ

'nokire-kilua433' is an npm package that has been identified as malicious, associated with a campaign that floods the npm registry with harmful packages.

The vulnerability can lead to the installation of malicious code that modifies your project's package metadata, potentially compromising its integrity and security.

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

Regularly audit your dependencies using tools like Vulert, which monitors for open-source vulnerabilities in real-time. You can check your application's status using the Vulert playground without any signup.

Detailed information can be found in the vulnerability report and through resources like Vulert, which helps track and alert for vulnerabilities in open-source packages.

How To Fix

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

npm uninstall nokire-kilua433

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