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

nokire-kore25 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-162712: Malicious code in nokire-kore25 (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 Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

The package 'nokire-kore25' is part of the npm ecosystem, which is widely used for JavaScript package management. It is designed to facilitate the development and sharing of JavaScript code. However, this package has been identified as part of a malicious campaign that floods npm with derivative packages to inflate developer reputation scores for token rewards. This behavior compromises the integrity of the npm registry and poses a significant risk to developers and their applications.

Vulnerability Detail

The vulnerability in 'nokire-kore25' originates from its association with the tea.xyz token reward campaign. It contains malicious scripts that modify the package.json file to remove private flags, alter version numbers, and generate random package names. This results in the continuous republishing of variants, polluting the npm registry and potentially leading to the installation of compromised packages by unsuspecting developers. The ramifications include loss of trust in the npm ecosystem and potential security risks for applications relying on these packages.

How To Fix

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

npm uninstall nokire-kore25

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 prevent the installation of this malicious package by using npm's package-lock.json file to lock down your dependencies. Ensure that your project does not include 'nokire-kore25' in its dependencies. You can also use the following command to uninstall it if it is already installed: 'npm uninstall nokire-kore25'.

Conclusion

The 'nokire-kore25' package poses a significant threat to the npm ecosystem due to its malicious behavior. Developers are urged to take immediate action by updating or removing the package to safeguard their applications. Utilizing tools like Vulert can help in monitoring and managing open-source vulnerabilities effectively.

See every vulnerability recorded for nokire-kore25 →

Share this vulnerability

FAQ

'nokire-kore25' is an npm package that has been identified as part of a malicious campaign to inflate developer reputation scores through the creation of derivative packages.

The vulnerability can lead to the installation of compromised packages, which may introduce security risks and affect the integrity of your application.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. By uploading your package-lock.json file to the Vulert playground, you can check for vulnerabilities without any signup.

If no patched version is available, it is advisable to remove the package from your project to mitigate any potential risks.

Regularly monitor your dependencies using tools like Vulert and keep your packages updated to the latest secure versions.

How To Fix

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

npm uninstall nokire-kore25

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