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

nokire-genji89 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-162582: Malicious code in nokire-genji89 (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 Penetration testing for web, API and mobile 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-genji89' is part of the npm ecosystem, which is widely used for JavaScript package management. This package is associated with the tea.xyz token reward campaign, which has been known to flood the npm registry with malicious packages. The primary functionality of such packages is to manipulate the npm registry for the purpose of inflating developer reputation scores through automated publishing of derivative packages.

Vulnerability Detail

The vulnerability in 'nokire-genji89' stems from its malicious code that modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior is part of a broader scheme to pollute the npm registry by continuously republishing variants of the package, thereby compromising the integrity of the ecosystem. The malicious payload can lead to unauthorized access and manipulation of projects that depend on this package, posing significant risks to developers and their applications.

How To Fix

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

npm uninstall nokire-genji89

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 prevent the installation of this malicious package by using npm's package-lock.json file to monitor your dependencies. Ensure that your project does not include 'nokire-genji89' and regularly audit your dependencies for any malicious packages.

Conclusion

The 'nokire-genji89' package poses a significant threat to the npm ecosystem due to its malicious code designed to manipulate the registry. It is essential for developers to be vigilant, regularly audit their dependencies, and utilize tools like Vulert to monitor for vulnerabilities. Immediate action should be taken to remove this package from any affected projects.

See every vulnerability recorded for nokire-genji89 →

Share this vulnerability

FAQ

'nokire-genji89' is an npm package that has been identified as containing malicious code intended to manipulate the npm registry.

You can check if your project is affected by using Vulert, which monitors your package-lock.json for vulnerabilities. Visit Vulert Scanner to use the Vulert playground without any signup.

If you have installed 'nokire-genji89', you should uninstall it immediately using 'npm uninstall nokire-genji89' and check your project for any unauthorized changes.

Yes, the impacts include unauthorized access to your project, potential data breaches, and the risk of your project being compromised through the polluted npm registry.

To prevent similar vulnerabilities, regularly audit your dependencies, use tools like Vulert for monitoring, and only install packages from trusted sources.

How To Fix

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

npm uninstall nokire-genji89

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