Malicious Code Injection in nokire-genji3: A Threat to npm Ecosystem
Summary
MAL-2025-162517: Malicious code in nokire-genji3 (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
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
Background
The package 'nokire-genji3' is part of a series of npm packages that emerged during the tea.xyz token reward campaign. These packages are designed to automate the generation and publication of derivative packages, often with randomized names, to inflate developer reputation scores for token rewards. This behavior poses a significant risk to the integrity of the npm ecosystem.
Vulnerability Detail
The vulnerability in 'nokire-genji3' originates from its malicious payload, which modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This leads to the continuous republishing of variants that pollute the npm registry, potentially compromising the security and reliability of applications that depend on these packages. The malicious code is designed to exploit the npm ecosystem by creating an overwhelming number of derivative packages, making it difficult for developers to identify legitimate packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall nokire-genji3If 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 measure, avoid using 'nokire-genji3' and any packages that may have been derived from it. Regularly audit your package dependencies using tools like npm audit to identify and mitigate vulnerabilities.
Conclusion
The 'nokire-genji3' package poses a significant threat to the npm ecosystem due to its malicious behavior of generating and republishing derivative packages. It is crucial for developers to be vigilant, regularly audit their dependencies, and utilize tools like Vulert to ensure their applications remain secure.
See every vulnerability recorded for nokire-genji3 →
FAQ
'nokire-genji3' is an npm package that is part of a malicious campaign aimed at inflating developer reputation scores through the automatic generation of derivative packages.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software. By analyzing your package-lock.json, Vulert can help you identify if your application is affected by this vulnerability.
If you have installed 'nokire-genji3', you should uninstall it immediately using 'npm uninstall nokire-genji3' and check for any other affected packages.
Yes, tools like Vulert can be used to monitor your dependencies for vulnerabilities in real-time. You can also use npm audit to check for known vulnerabilities in your project.
Using malicious packages can lead to compromised application security, data breaches, and a polluted package registry, making it difficult to find reliable packages.
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
