Malicious Code Injection in nokire-genji10: A Threat to npm Users
Summary
MAL-2025-162495: Malicious code in nokire-genji10 (npm). Affected versions are not published. No fix is published. How to fix ↓
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.
No signup required · Results in about 60 seconds
Background
The package 'nokire-genji10' is part of the npm ecosystem, which is widely used for JavaScript package management. It is associated with the tea.xyz token reward campaign, which has been known to flood the npm registry with malicious packages. These packages often contain scripts designed to manipulate package metadata and inflate developer reputation scores, posing a significant risk to users and the integrity of the npm registry.
Vulnerability Detail
The vulnerability in 'nokire-genji10' originates from its design to include malicious scripts that modify the package.json file. This includes removing private flags, altering version numbers, and generating random package names, which leads to the continuous republishing of these variants. The ramifications of this vulnerability include the potential for developers to unknowingly publish compromised packages, which can lead to 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-genji10If 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 dependencies. Ensure that your project does not include 'nokire-genji10' in its dependencies.
Conclusion
The 'nokire-genji10' package poses a significant threat due to its malicious code designed to manipulate package metadata. Users are advised to uninstall this package and monitor their dependencies closely. Utilizing tools like Vulert can help in identifying vulnerabilities in real-time, ensuring the security of your applications.
See every vulnerability recorded for nokire-genji10 →
FAQ
The main risk is the potential for malicious code to be executed, which can compromise the integrity of your application and lead to security vulnerabilities.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check your application without requiring any signup.
You should uninstall the package immediately using the command 'npm uninstall nokire-genji10' and check for any other affected packages.
Currently, there are no known patches for the nokire-genji10 package. The best course of action is to remove it from your project.
Using compromised packages can lead to unauthorized access, data breaches, and a loss of trust in your software, potentially affecting users and stakeholders.
