Malicious Code Injection in nokire-genji68: A Threat to npm Packages
Summary
MAL-2025-162559: Malicious code in nokire-genji68 (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-genji68' is part of the npm ecosystem, which is widely used for JavaScript package management. This package is associated with the tea.xyz token reward campaign, which has been linked to a series of malicious activities aimed at inflating developer reputation scores. The package's functionality is compromised by scripts that automatically generate and publish derivative packages, leading to potential pollution of the npm registry.
Vulnerability Detail
The vulnerability in 'nokire-genji68' originates from its design to include autopublish scripts that modify the package.json file. These modifications remove private flags, alter version numbers, and create random package names, which can lead to the proliferation of malicious packages in the npm registry. The ramifications include damage to developer reputations, potential security risks for applications relying on these packages, and overall degradation of the npm ecosystem.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall nokire-genji68If 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-genji68' package altogether. If it is a dependency of another package, consider using alternative packages that do not have known vulnerabilities. Additionally, you can monitor your package-lock.json file for any changes and remove any suspicious packages.
Conclusion
The 'nokire-genji68' package poses a significant threat due to its malicious code that alters package configurations and floods the npm registry. It is crucial for developers to remove this package and monitor their dependencies to maintain the integrity of their applications.
See every vulnerability recorded for nokire-genji68 →
FAQ
The main issue is that it contains malicious code designed to modify package.json files and flood the npm registry with derivative packages.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software. Visit the Vulert playground at Vulert Scanner to check your application without needing to sign up.
You should uninstall the package immediately using 'npm uninstall nokire-genji68' and check for any other dependencies that may be affected.
Yes, consider using other reputable packages that provide similar functionality without the associated risks.
Regularly audit your dependencies, use tools like Vulert for real-time monitoring, and stay updated on security advisories related to the packages you use.
