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

nokire-kore12 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-162698: Malicious code in nokire-kore12 (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 Your last release was probably never penetration tested 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-kore12' is part of a malicious campaign targeting the npm ecosystem, specifically designed to exploit developers' reputation systems. It is associated with the tea.xyz token reward initiative, which aims to inflate developer scores by flooding the npm registry with derivative packages. The package's functionality includes generating and publishing random package names, which can lead to significant pollution of the npm registry.

Vulnerability Detail

The vulnerability in 'nokire-kore12' arises from its malicious code that modifies the package.json file to remove private flags and change version numbers. It generates random package names, primarily themed around Indonesian culture, and continuously republishes these variants. This behavior not only compromises the integrity of the npm registry but also poses a risk to developers who may unknowingly install these malicious packages, potentially leading to further exploitation or data breaches.

How To Fix

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

npm uninstall nokire-kore12

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-kore12' and any packages that depend on it. Ensure that your package-lock.json file does not include this package. You can also use the following command to remove it: npm uninstall nokire-kore12.

Conclusion

The 'nokire-kore12' package poses a significant threat to the npm ecosystem due to its malicious behavior aimed at inflating developer reputation scores. It is essential to take immediate action to remove this package and monitor your dependencies for any potential vulnerabilities.

See every vulnerability recorded for nokire-kore12 →

Share this vulnerability

FAQ

'nokire-kore12' is an npm package involved in a malicious campaign that aims to inflate developer reputation scores by flooding the npm registry with derivative packages.

The vulnerability can lead to the installation of malicious code, which may compromise your project's security and integrity, potentially leading to data breaches or further exploitation.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software. By checking your package-lock.json file, you can identify if your application is affected by this vulnerability.

Immediately uninstall the package using 'npm uninstall nokire-kore12' and audit your dependencies to ensure no other malicious packages are present.

Regularly audit your dependencies, use tools like Vulert to monitor for vulnerabilities, and stay informed about the latest security advisories in the open-source community.

How To Fix

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

npm uninstall nokire-kore12

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