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

nokire-kore26 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-162713: Malicious code in nokire-kore26 (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-kore26' is part of a broader malicious campaign targeting the npm ecosystem, specifically linked to the tea.xyz token reward initiative. This package is designed to manipulate the npm registry by generating and publishing derivative packages with randomized names. 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-kore26' originates from its malicious design, which includes scripts that modify the package.json file to remove private flags, alter version numbers, and create random package names. This behavior leads to the continuous republishing of variants, polluting the npm registry and potentially compromising other packages by introducing malicious code. The ramifications include loss of trust in the npm ecosystem, potential data breaches, and exploitation of affected applications.

How To Fix

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

npm uninstall nokire-kore26

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 prevent the installation of 'nokire-kore26' by using npm's package-lock.json to monitor dependencies. If you suspect that your project is affected, consider using the following command to audit your dependencies: npm audit. Additionally, you can use Vulert to monitor your project for vulnerabilities without requiring code access.

Conclusion

The 'nokire-kore26' package poses a significant threat to the npm ecosystem due to its malicious behavior aimed at manipulating the registry. It is crucial to take immediate action to remove this package and monitor your project for vulnerabilities. Utilizing tools like Vulert can help maintain the security of your applications.

See every vulnerability recorded for nokire-kore26 →

Share this vulnerability

FAQ

'nokire-kore26' is a malicious npm package associated with a token reward campaign that aims to inflate developer reputation scores.

The vulnerability can lead to the introduction of malicious code into your application, compromising its security and integrity.

Immediately remove the 'nokire-kore26' package from your project and audit your dependencies for any other vulnerabilities.

Yes, you can use Vulert, which monitors your package-lock.json to alert you in real-time for open-source vulnerabilities.

You can use the Vulert playground at Vulert Scanner to check if your application is affected without signing up.

How To Fix

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

npm uninstall nokire-kore26

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