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

nokire-kore35 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-162723: Malicious code in nokire-kore35 (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-kore35' is part of a broader malicious campaign targeting the npm ecosystem, specifically linked to the tea.xyz token reward initiative. This package is designed to manipulate npm's package registry by generating and publishing numerous derivative packages with randomized names, which can inflate developer reputation scores. Its primary functionality revolves around automatic publishing scripts that compromise the integrity of the npm registry.

Vulnerability Detail

The vulnerability in 'nokire-kore35' stems from its malicious payload that modifies the package.json file by removing private flags, altering version numbers, and creating random package names. This behavior not only pollutes the npm registry but also poses a significant risk to developers who may unknowingly install these compromised packages, leading to potential security breaches and loss of trust in the npm ecosystem.

How To Fix

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

npm uninstall nokire-kore35

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-kore35' package and monitor your project for any dependencies that may have been affected. Additionally, consider using tools like Vulert to monitor your package-lock.json for vulnerabilities in real-time.

Conclusion

The 'nokire-kore35' package represents a significant threat to the npm ecosystem, with its malicious activities capable of compromising developer projects. It is crucial for developers to remain vigilant, regularly audit their dependencies, and utilize tools like Vulert to safeguard their applications against such vulnerabilities.

See every vulnerability recorded for nokire-kore35 →

Share this vulnerability

FAQ

'nokire-kore35' is a malicious npm package involved in a campaign that aims to inflate developer reputation scores through the automatic generation and publishing of derivative packages.

The vulnerability can lead to the installation of compromised packages, which may introduce security risks and affect the integrity of your project.

You should uninstall 'nokire-kore35' immediately using the command 'npm uninstall nokire-kore35' and check for any other potentially malicious packages.

Regularly update your packages, use trusted sources, and consider employing tools like Vulert to monitor your dependencies for vulnerabilities.

Vulert is a tool that monitors your package-lock.json for open-source vulnerabilities in real-time. You can use the Vulert playground to check if your application is affected by known vulnerabilities without any signup.

How To Fix

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

npm uninstall nokire-kore35

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