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

nokire-genji23 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-162510: Malicious code in nokire-genji23 (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-genji23' 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 aims to exploit the npm registry by flooding it with derivative packages. These packages are designed to inflate developer reputation scores through automated publishing scripts, which can lead to significant pollution of the npm registry and compromise the integrity of the ecosystem.

Vulnerability Detail

The vulnerability in 'nokire-genji23' originates from its association with the tea.xyz token reward campaign. The package contains malicious scripts that modify the package.json file by removing private flags, altering version numbers, and generating random package names. This behavior can lead to unauthorized access, reputation damage for developers, and a polluted npm registry, making it difficult for legitimate packages to be discovered and used.

How To Fix

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

npm uninstall nokire-genji23

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-genji23' package and monitor your project for any dependencies that may rely on it. Regularly check your package-lock.json file for any signs of this malicious package and remove it if found.

Conclusion

The 'nokire-genji23' package poses a significant threat to the npm ecosystem due to its malicious behavior. It is crucial for developers to be vigilant, regularly audit their dependencies, and utilize tools like Vulert to monitor for vulnerabilities. By taking proactive measures, developers can protect their projects and maintain the integrity of the npm registry.

See every vulnerability recorded for nokire-genji23 →

Share this vulnerability

FAQ

'nokire-genji23' is an npm package identified as part of a malicious campaign that floods the npm registry with derivative packages.

This vulnerability can lead to unauthorized modifications in your project, reputation damage, and pollution of the npm registry, making it harder to find legitimate packages.

You should uninstall 'nokire-genji23' immediately using 'npm uninstall nokire-genji23' and check your project for any other affected dependencies.

You can use Vulert, which monitors and alerts in real-time for open-source vulnerabilities using just your package-lock.json. You can check your application for vulnerabilities using the Vulert playground at Vulert Scanner without any signup.

Regularly update your dependencies, use tools like Vulert for monitoring, and audit your packages to identify any potential vulnerabilities.

How To Fix

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

npm uninstall nokire-genji23

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