Malicious Code Injection in nokire-genji799 Package

nokire-genji799 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-162572: Malicious code in nokire-genji799 (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 nokire-genji799 package 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 a polluted registry and potential security risks for users.

Vulnerability Detail

The vulnerability in the nokire-genji799 package stems from its malicious code that modifies the package.json file to remove private flags and changes 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 risks to developers who may unknowingly install these malicious packages, leading to potential data breaches or system compromises.

How To Fix

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

npm uninstall nokire-genji799

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

There are no specific workarounds for this vulnerability other than avoiding the use of the nokire-genji799 package. If you suspect that your project may be affected, consider using tools like Vulert to monitor your dependencies. You can check your application for vulnerabilities using the Vulert playground at https://vulert.com/scanner without any signup.

Conclusion

The nokire-genji799 package poses a significant security risk due to its malicious code that alters package metadata and floods the npm registry with unwanted variants. It is crucial for developers to be vigilant and remove such packages from their projects, as well as utilize monitoring tools like Vulert to stay informed about potential vulnerabilities.

See every vulnerability recorded for nokire-genji799 →

Share this vulnerability

FAQ

The nokire-genji799 package is an npm package that has been identified as part of a malicious campaign to exploit the npm registry.

The malicious code modifies your package.json file, removes private flags, and can lead to the installation of unwanted and potentially harmful packages.

You should uninstall the nokire-genji799 package immediately using the command npm uninstall nokire-genji799.

While many packages in the npm registry are safe, it is essential to review and monitor your dependencies regularly for any vulnerabilities.

You can use tools like Vulert, which monitors your package-lock.json file for open-source vulnerabilities in real-time. You can check your application at Vulert Scanner.

How To Fix

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

npm uninstall nokire-genji799

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