Malicious Code Injection in nokire-zenitsu20: A Threat to npm Ecosystem
Summary
MAL-2025-163607: Malicious code in nokire-zenitsu20 (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-zenitsu20' is part of a broader campaign targeting the npm ecosystem, where malicious actors deploy packages to exploit developer reputation systems. These packages are designed to automatically generate and publish derivative versions with altered metadata, which can mislead users and inflate the reputation of the attackers. The malicious nature of this package poses a significant risk to developers and users relying on npm for secure and reliable packages.
Vulnerability Detail
The vulnerability in 'nokire-zenitsu20' stems from its association with the tea.xyz token reward campaign, which has been flooding the npm registry with malicious packages. The package contains scripts that modify the 'package.json' file to remove private flags, alter version numbers, and generate random package names. This behavior not only pollutes the npm registry but also compromises the integrity of the development environment, potentially leading to further exploitation and misuse of developer tools.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall nokire-zenitsu20If 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-zenitsu20' package altogether. Instead, consider using alternative packages that provide similar functionality without the associated risks. Always verify the integrity and reputation of packages before including them in your project.
Conclusion
The 'nokire-zenitsu20' package represents a significant threat to the npm ecosystem due to its malicious code and the potential for widespread exploitation. Developers must take proactive measures to secure their projects by removing this package and monitoring their dependencies for vulnerabilities. Utilizing tools like Vulert can aid in maintaining a secure development environment.
See every vulnerability recorded for nokire-zenitsu20 →
FAQ
The main risk is that it contains malicious code that alters package metadata and floods the npm registry with unwanted variants, compromising the integrity of the development environment.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check if your application is affected without requiring any signup.
You should uninstall the package immediately using 'npm uninstall nokire-zenitsu20' and review your dependencies for any other potentially malicious packages.
Yes, there are many reputable packages available on npm that provide similar functionality. Always check the package's documentation and user reviews before installation.
Regularly update your dependencies, use tools like Vulert for monitoring vulnerabilities, and only install packages from trusted sources.
