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

nokire-kore37 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-162725: Malicious code in nokire-kore37 (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 Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

Background

The package 'nokire-kore37' is part of a broader campaign targeting the npm ecosystem, specifically linked to the tea.xyz token reward initiative. This package is designed to automate the generation and publication of derivative packages, which can lead to reputation inflation for developers involved in the tea protocol. Its functionality is compromised due to the presence of malicious scripts that manipulate package metadata.

Vulnerability Detail

The vulnerability in 'nokire-kore37' originates from its association with a malicious campaign that floods the npm registry with derivative packages. The malicious payload alters the package.json file by removing private flags, changing version numbers, and generating random package names. This not only pollutes the npm registry but also poses a risk to developers who may unknowingly use these compromised packages, potentially leading to security breaches and loss of trust in the npm ecosystem.

How To Fix

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

npm uninstall nokire-kore37

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 'nokire-kore37' and any packages that depend on it. Regularly audit your package-lock.json file for any signs of this package and remove it if found. You can also use tools like Vulert to monitor your project for vulnerabilities.

Conclusion

The 'nokire-kore37' package poses a significant threat to the npm ecosystem due to its malicious code that manipulates package metadata. It is crucial for developers to remove this package from their projects and to utilize tools like Vulert for ongoing monitoring of vulnerabilities.

See every vulnerability recorded for nokire-kore37 →

Share this vulnerability

FAQ

'nokire-kore37' is an npm package that has been identified as part of a malicious campaign aimed at inflating developer reputation scores through automated package publication.

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

You should uninstall the package immediately using 'npm uninstall nokire-kore37' and check for any dependencies that may be affected.

Regularly audit your dependencies, use tools like Vulert to monitor for vulnerabilities, and stay informed about the packages you include in your projects.

Yes, you can use the Vulert playground at Vulert Scanner to check your application for vulnerabilities without needing to sign up.

Sponsored Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

How To Fix

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

npm uninstall nokire-kore37

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