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

nokire-kore14 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-162700: Malicious code in nokire-kore14 (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-kore14' is part of a broader campaign that exploits the npm ecosystem, primarily targeting developers involved in token reward systems. This package is designed to automate the generation and publication of derivative packages, which can lead to reputation inflation within the npm registry. Its malicious nature stems from scripts that modify package metadata and continuously republish variants, thereby polluting the registry.

Vulnerability Detail

The vulnerability in 'nokire-kore14' originates from its association with the tea.xyz token reward campaign. It contains scripts that remove private flags from package.json, alter version numbers, and generate random package names. This behavior can lead to the proliferation of malicious packages in the npm registry, potentially compromising the integrity of applications that depend on these packages. The continuous republishing of these variants can also clutter the registry, making it difficult for developers to find legitimate packages.

How To Fix

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

npm uninstall nokire-kore14

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 workaround, you can manually check your package-lock.json file for any instances of 'nokire-kore14' and remove it. You can do this by running the following command in your terminal: npm uninstall nokire-kore14. Additionally, consider using tools like Vulert to monitor your dependencies for vulnerabilities.

Conclusion

The 'nokire-kore14' package poses a significant threat to npm users due to its malicious code that modifies package metadata and repopulates the npm registry with harmful variants. It is crucial to remove this package and monitor your dependencies for vulnerabilities to maintain the security of your applications.

See every vulnerability recorded for nokire-kore14 →

Share this vulnerability

FAQ

'nokire-kore14' is an npm package associated with a malicious campaign that aims to inflate developer reputation scores through automated package publishing.

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

You should uninstall 'nokire-kore14' immediately to prevent any potential security risks.

Currently, there is no patched version available for 'nokire-kore14'. The best course of action is to remove the package entirely.

You can use Vulert, which monitors your package-lock.json for vulnerabilities in real-time. You can check your application using the Vulert playground at Vulert Scanner without needing to sign up.

How To Fix

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

npm uninstall nokire-kore14

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