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

nokire-kore11 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-162697: Malicious code in nokire-kore11 (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-kore11' is part of the npm ecosystem, which is widely used for JavaScript package management. It is associated with the tea.xyz token reward campaign, which has been known to flood the npm registry with malicious packages. These packages often contain scripts designed to manipulate package metadata and inflate developer reputation scores, posing significant risks to users and the integrity of the npm registry.

Vulnerability Detail

The vulnerability in 'nokire-kore11' stems from its malicious code that modifies the package.json file. This code removes private flags, alters version numbers, and generates random package names, leading to the continuous republishing of these variants. The origin of this vulnerability is linked to the tea.xyz token reward campaign, which aims to exploit the npm registry by creating derivative packages with the intent of polluting the registry and misleading developers.

How To Fix

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

npm uninstall nokire-kore11

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, you can avoid using 'nokire-kore11' and any other packages associated with the tea.xyz campaign. Monitor your package-lock.json file for any unauthorized changes and consider using tools like Vulert to keep track of vulnerabilities in your dependencies.

Conclusion

The 'nokire-kore11' package poses a significant threat due to its malicious code that alters package metadata and floods the npm registry. It is essential to remove this package and monitor your dependencies for vulnerabilities to maintain the integrity of your projects.

See every vulnerability recorded for nokire-kore11 →

Share this vulnerability

FAQ

'nokire-kore11' is an npm package that has been identified as malicious, part of a campaign to exploit the npm registry.

The malicious code modifies your package.json, potentially leading to unauthorized changes and the pollution of the npm registry.

You should uninstall 'nokire-kore11' immediately using 'npm uninstall nokire-kore11' and check for any other affected packages.

You can use Vulert, which monitors your package-lock.json for vulnerabilities in real-time without requiring code access or installation.

Yes, you can use the Vulert playground at Vulert Scanner to check for vulnerabilities in your application without any signup.

How To Fix

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

npm uninstall nokire-kore11

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