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

nokire-kore40 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-162729: Malicious code in nokire-kore40 (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-kore40' is part of the npm ecosystem, which is widely used for JavaScript package management. This package has been identified as part of a malicious campaign that floods npm with harmful packages. Its primary function is to manipulate the npm registry by creating and publishing numerous derivative packages with altered metadata, thereby inflating developer reputation scores for token rewards.

Vulnerability Detail

The vulnerability in 'nokire-kore40' stems from its involvement in a malicious campaign that modifies the package.json file to remove private flags and change version numbers. It generates random package names, often themed around Indonesian culture, and continuously republishes these variants to pollute the npm registry. This behavior not only compromises the integrity of the npm ecosystem but also poses risks to developers who may unknowingly use these tainted packages.

How To Fix

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

npm uninstall nokire-kore40

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, avoid using the 'nokire-kore40' package and monitor your dependencies for any similar malicious packages. Regularly audit your npm packages using npm audit to identify vulnerabilities.

Conclusion

The 'nokire-kore40' package poses a significant threat to the npm ecosystem due to its malicious behavior of modifying package metadata and republishing harmful variants. It is essential for developers to remove this package and monitor their dependencies to maintain the integrity of their projects.

See every vulnerability recorded for nokire-kore40 →

Share this vulnerability

FAQ

'nokire-kore40' is an npm package identified as part of a malicious campaign that modifies package metadata to inflate developer reputation scores.

Using 'nokire-kore40' can compromise your project's integrity by introducing malicious code and potentially leading to security breaches.

You should uninstall 'nokire-kore40' immediately using the command: npm uninstall nokire-kore40.

You can use tools like npm audit to check for vulnerabilities in your dependencies. Additionally, consider using Vulert, which monitors your package-lock.json for open-source vulnerabilities in real-time.

Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring any signup.

How To Fix

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

npm uninstall nokire-kore40

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