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

nokire-kore8 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-162738: Malicious code in nokire-kore8 (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-kore8' is part of a series of malicious packages that emerged during the tea.xyz token reward campaign. These packages are designed to manipulate the npm registry by creating and publishing numerous derivative packages with random names, thereby inflating developer reputation scores for token rewards. The malicious nature of this package poses a significant risk to developers and users relying on npm for package management.

Vulnerability Detail

The vulnerability in 'nokire-kore8' originates from its design to execute autopublish scripts that modify the package.json file. This modification removes private flags, alters version numbers, and generates random package names, leading to the continuous republishing of these variants. The ramifications include pollution of the npm registry, potential security risks for users who inadvertently install these packages, and a compromised reputation for legitimate developers.

How To Fix

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

npm uninstall nokire-kore8

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, avoid using the 'nokire-kore8' package and monitor your project for any unintended installations. You can also use tools like Vulert to scan your package-lock.json file for vulnerabilities. For example, you can visit the Vulert playground at https://vulert.com/scanner to check if your application is affected by this vulnerability without needing to sign up.

Conclusion

The 'nokire-kore8' package represents a significant threat to npm users due to its malicious intent to manipulate the npm registry. It is crucial for developers to be vigilant, remove any instances of this package, and utilize tools like Vulert to monitor for vulnerabilities in their projects.

See every vulnerability recorded for nokire-kore8 →

Share this vulnerability

FAQ

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

This vulnerability can lead to the pollution of the npm registry and may expose your project to security risks if the malicious package is inadvertently installed.

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

You can use Vulert, which monitors your package-lock.json file for open-source vulnerabilities in real-time. Visit Vulert Scanner to check your application without signing up.

There are no patches available for 'nokire-kore8' as it is a malicious package. The best course of action is to remove it from your project.

How To Fix

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

npm uninstall nokire-kore8

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