Malicious Code Injection in nokire-zenitsu23: A Threat to npm Packages
Summary
MAL-2025-163610: Malicious code in nokire-zenitsu23 (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-zenitsu23' is part of a series of npm packages associated with the tea.xyz token reward campaign. These packages are designed to automatically generate and publish derivative packages with randomized names, aimed at inflating developer reputation scores for token rewards. The malicious nature of this package lies in its ability to modify critical files and republish variants, thus polluting the npm registry.
Vulnerability Detail
The vulnerability in 'nokire-zenitsu23' originates from its design to include autopublish scripts that alter the package.json file by removing private flags and changing version numbers. This allows the package to generate random names and continuously republish variants, leading to potential misuse of the npm registry and a degradation of trust in the ecosystem. The malicious payload can affect developers by compromising their projects and reputations.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall nokire-zenitsu23If 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-zenitsu23' package and monitor your project for any dependencies that may have included it. Regularly check your package-lock.json file for any unexpected changes or additions.
Conclusion
The 'nokire-zenitsu23' package poses a significant threat due to its malicious code that modifies essential files and repopulates the npm registry with harmful variants. It is crucial for developers to take immediate action by removing this package and employing monitoring tools to safeguard their projects.
See every vulnerability recorded for nokire-zenitsu23 →
FAQ
The primary risk is that it modifies package.json files and republish variants, which can lead to a polluted npm registry and compromised developer reputations.
You can use tools like Vulert, which monitors your package-lock.json for vulnerabilities in real-time. Visit Vulert Scanner to check if your application is affected.
You should immediately uninstall the package using 'npm uninstall nokire-zenitsu23' and review your project for any other potentially malicious dependencies.
Yes, tools like Vulert can help monitor your project for open-source vulnerabilities without requiring code access or installation.
Regularly update your packages, review your dependencies, and use vulnerability monitoring tools like Vulert to stay informed about potential threats.
