Malicious Code Injection in nokire-genji18: A Threat to npm Ecosystem
Summary
MAL-2025-162504: Malicious code in nokire-genji18 (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-genji18' is part of the npm ecosystem, which is widely used for JavaScript package management. It is often utilized in various applications to enhance functionality through reusable code. However, this package has been identified as part of a malicious campaign that aims to exploit the npm registry by flooding it with derivative packages, thereby inflating developer reputation scores for token rewards.
Vulnerability Detail
The vulnerability in 'nokire-genji18' stems from its involvement in a malicious campaign that 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, which pollutes the npm registry and poses a significant risk to developers relying on the integrity of packages in the ecosystem. The malicious code is designed to execute autopublish scripts that automate the creation and distribution of these harmful packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall nokire-genji18If 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, you can avoid using 'nokire-genji18' and any packages that may have been derived from it. Regularly audit your package-lock.json file to identify any potentially malicious packages. You can also use the following command to check for vulnerabilities in your project: 'npm audit'.
Conclusion
The 'nokire-genji18' package poses a significant threat to the npm ecosystem due to its malicious behavior. It is essential for developers to remain vigilant, regularly audit their dependencies, and utilize tools like Vulert to monitor for vulnerabilities. By taking proactive measures, you can safeguard your projects from potential risks associated with malicious packages.
See every vulnerability recorded for nokire-genji18 →
FAQ
'nokire-genji18' is an npm package that has been identified as part of a malicious campaign to exploit the npm registry.
The vulnerability can lead to the injection of malicious code into your project, potentially compromising its security and integrity.
You should uninstall the package immediately using 'npm uninstall nokire-genji18' and audit your project for any other vulnerabilities.
You can use tools like Vulert, which monitors your package-lock.json file for vulnerabilities in real-time without requiring code access or installation.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.
