Malicious Code Injection in nokire-genji66: A Threat to npm Ecosystem
Summary
MAL-2025-162557: Malicious code in nokire-genji66 (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-genji66' 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 various packages. This package, like others in the campaign, is designed to manipulate the npm registry by generating and publishing derivative packages with altered metadata, thus inflating developer reputation scores for token rewards.
Vulnerability Detail
The vulnerability in 'nokire-genji66' originates from its malicious design to modify the package.json file by removing private flags and changing version numbers. It generates random package names, often themed around Indonesian culture, and continuously republishes these variants to pollute the npm registry. This behavior can lead to a compromised npm environment, where developers may inadvertently install malicious packages, risking their applications' integrity and security.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall nokire-genji66If 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 avoid using the 'nokire-genji66' package and monitor your dependencies for any malicious activity. Additionally, consider using tools like Vulert to monitor your package-lock.json file for vulnerabilities without needing to access the code directly.
Conclusion
The 'nokire-genji66' package poses a significant risk to the npm ecosystem due to its malicious behavior of altering package metadata and republishing variants. It is crucial for developers to be vigilant, remove such packages, and utilize monitoring tools like Vulert to safeguard their applications from potential threats.
See every vulnerability recorded for nokire-genji66 →
FAQ
The primary threat is the modification of package metadata, which can lead to the installation of malicious packages and compromise application security.
You can use the Vulert playground at Vulert Scanner to check your application for vulnerabilities without any signup.
You should uninstall the package immediately using 'npm uninstall nokire-genji66' and monitor your project for any unusual behavior.
Yes, Vulert provides real-time monitoring and alerts for open-source vulnerabilities using just your package-lock.json file.
Using compromised packages can lead to data breaches, unauthorized access, and significant security risks for your applications and users.
