Malicious Code Injection in nokire-kore13: A Threat to npm Packages

nokire-kore13 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-162699: Malicious code in nokire-kore13 (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-kore13' is part of a series of npm packages that have been associated with the tea.xyz token reward campaign. These packages are designed to inflate developer reputation scores by automatically generating and publishing derivative packages with randomized names. This behavior not only clutters the npm registry but also poses significant risks to developers and users relying on these packages.

Vulnerability Detail

The vulnerability in 'nokire-kore13' stems from its malicious payload, which modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This manipulation allows the package to continuously republish variants, polluting the npm registry and potentially compromising the integrity of applications that depend on these packages. The origin of this issue is linked to automated scripts designed to exploit the npm ecosystem for token rewards.

How To Fix

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

npm uninstall nokire-kore13

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 'nokire-kore13' by adding it to your project's .npmrc file with the following entry: 'package-lock=false'. This will stop npm from installing this package until a permanent fix is applied.

Conclusion

The 'nokire-kore13' package poses a significant threat due to its malicious code designed to manipulate the npm registry. It is essential for developers to remove this package and monitor their projects for vulnerabilities. Utilizing tools like Vulert can help maintain the security of your applications.

See every vulnerability recorded for nokire-kore13 →

Share this vulnerability

FAQ

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

The vulnerability can lead to the installation of malicious code that modifies your application's dependencies, potentially compromising its security and functionality.

You should immediately remove 'nokire-kore13' from your project and check for any unauthorized changes in your package.json file.

Yes, you can use tools like Vulert, which monitors your package-lock.json for open-source vulnerabilities in real-time. You can also check your application against known vulnerabilities using the Vulert playground.

Regularly update your dependencies, use trusted packages, and employ vulnerability scanning tools to identify and mitigate risks.

How To Fix

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

npm uninstall nokire-kore13

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