Malicious Code Injection in nokire-genji20: A Threat to npm Ecosystem
Summary
MAL-2025-162507: Malicious code in nokire-genji20 (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-genji20' is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to generate and publish derivative packages with randomized names, aiming to inflate developer reputation scores for token rewards. Its functionality revolves around automatic publishing scripts that can compromise the integrity of the npm registry.
Vulnerability Detail
The vulnerability in 'nokire-genji20' stems from its malicious payload, which modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior leads to the continuous republishing of variants, polluting the npm registry and potentially harming developers' reputations and project integrity. The origin of this issue is linked to the broader trend of malicious packages flooding the npm ecosystem, specifically targeting token reward campaigns.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall nokire-genji20If 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 lock your dependencies. Additionally, consider using the following command to audit your packages for vulnerabilities: npm audit.
Conclusion
The 'nokire-genji20' package poses a significant threat to the npm ecosystem due to its malicious behavior. It is essential for developers to be vigilant about the packages they use and to take proactive measures to secure their projects against such vulnerabilities.
See every vulnerability recorded for nokire-genji20 →
FAQ
The primary risk is the modification of package.json files, which can lead to the exposure of private data and the proliferation of malicious packages in the npm registry.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check your application without any signup.
You should immediately remove the package from your project and check for any updates or patches that may address the vulnerability.
While specific exploits have not been detailed, the behavior of the package suggests it can lead to significant reputational damage and project integrity issues.
Yes, regularly audit your dependencies using tools like npm audit and monitor your packages with services like Vulert to stay informed about vulnerabilities.
