Malicious Code Injection in nokire-zenitsu42: A Threat to npm Ecosystem
Summary
MAL-2025-163631: Malicious code in nokire-zenitsu42 (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
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
Background
The package nokire-zenitsu42 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 known to flood npm with malicious packages. The primary function of such packages is to inflate developer reputation scores through automated publishing of derivative packages, which can lead to significant pollution of the npm registry.
Vulnerability Detail
The vulnerability in nokire-zenitsu42 originates from its design to include autopublish scripts that modify the package.json file. These modifications remove private flags, alter version numbers, and generate random package names, which can lead to the proliferation of malicious variants in the npm registry. The ramifications include potential security risks for developers who unknowingly install these packages, as they may introduce vulnerabilities into their applications.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall nokire-zenitsu42If 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 workaround, you can avoid using the nokire-zenitsu42 package altogether. If it is already part of your project, consider removing it and replacing it with a trusted alternative. Additionally, you can monitor your package dependencies using tools like Vulert, which can alert you to vulnerabilities in real-time without requiring code access or installation.
Conclusion
The nokire-zenitsu42 package poses a significant risk due to its malicious code designed to manipulate package metadata and proliferate harmful variants in the npm registry. It is crucial for developers to be aware of such vulnerabilities and take proactive measures to secure their applications.
See every vulnerability recorded for nokire-zenitsu42 →
FAQ
Nokire-zenitsu42 is an npm package that is part of a malicious campaign aimed at inflating developer reputation scores through automated publishing.
If your application uses nokire-zenitsu42, it may inadvertently introduce security risks and vulnerabilities due to the malicious modifications made by the package.
You can use Vulert's playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.
If you have installed nokire-zenitsu42, it is advisable to remove it from your project and replace it with a trusted alternative.
Yes, you can use Vulert to monitor your package-lock.json file for real-time alerts on open-source vulnerabilities in your software.
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
