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

nokire-kore22 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-162709: Malicious code in nokire-kore22 (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-kore22' is part of a series of malicious npm packages associated with the tea.xyz token reward campaign. These packages are designed to manipulate the npm registry by automatically generating and publishing derivative packages with randomized names. This behavior aims to inflate developer reputation scores for token rewards, posing a significant risk to the integrity of the npm ecosystem.

Vulnerability Detail

The vulnerability in 'nokire-kore22' originates from its malicious code that modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This results in the continuous republishing of variants, which pollutes the npm registry and can lead to the exploitation of unsuspecting developers who may unknowingly use these compromised packages. The malicious payload is designed to operate stealthily, making it difficult for users to detect the changes made to their projects.

How To Fix

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

npm uninstall nokire-kore22

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 avoid using the 'nokire-kore22' package and instead look for alternative packages that provide similar functionality without the associated risks. Additionally, regularly audit your npm packages using tools like 'npm audit' to identify and mitigate vulnerabilities.

Conclusion

The 'nokire-kore22' package poses a significant threat to npm users due to its malicious code designed to manipulate the npm registry. It is essential to remove this package and any related dependencies from your projects to maintain security. Regular audits and the use of monitoring tools like Vulert can help safeguard against such vulnerabilities in the future.

See every vulnerability recorded for nokire-kore22 →

Share this vulnerability

FAQ

'nokire-kore22' is a malicious npm package involved in a scheme to inflate developer reputation scores through automated publishing of compromised packages.

You can use tools like Vulert, which monitors your package-lock.json for vulnerabilities in real-time. Visit Vulert Scanner to check if your application is affected without needing to sign up.

Using compromised packages can lead to unauthorized access to your project, data leaks, and potential exploitation of your application by malicious actors.

It is recommended to audit your npm packages regularly, especially before deploying updates or new features, to ensure that you are not using any vulnerable packages.

If you find a vulnerability, remove the affected package immediately, update your project dependencies, and monitor for any further vulnerabilities using tools like Vulert.

How To Fix

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

npm uninstall nokire-kore22

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