Malicious Code Injection in nokire-zenitsu5: A Threat to npm Ecosystem
Summary
MAL-2025-163639: Malicious code in nokire-zenitsu5 (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-zenitsu5' 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 the npm registry with malicious packages. These packages often contain scripts that manipulate package metadata and publish numerous derivative packages, potentially harming developers' reputations and polluting the registry.
Vulnerability Detail
The vulnerability in 'nokire-zenitsu5' stems from its malicious code that modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior is designed to inflate developer reputation scores for token rewards while continuously republishing variants, leading to registry pollution. The origin of this vulnerability is linked to the tea.xyz token reward campaign, which exploits npm's publishing mechanisms.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall nokire-zenitsu5If 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 remove the 'nokire-zenitsu5' package from your project by executing 'npm uninstall nokire-zenitsu5'. Additionally, consider using npm audit to identify and mitigate vulnerabilities in your project.
Conclusion
The 'nokire-zenitsu5' package poses a significant threat due to its malicious code designed to manipulate npm's package management system. It is essential for developers to stay vigilant, regularly update their dependencies, and utilize tools like Vulert for real-time vulnerability monitoring.
See every vulnerability recorded for nokire-zenitsu5 →
FAQ
The primary risk is the potential for malicious code to alter your project's package.json file, leading to unauthorized package republishing and reputation inflation.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit their playground at Vulert Scanner to check your application without needing to sign up.
If an immediate update is not possible, consider uninstalling the package and monitoring your project for any unusual behavior or vulnerabilities.
Yes, tools like npm audit can help identify vulnerabilities in your project, and services like Vulert provide real-time monitoring for open-source vulnerabilities.
Using compromised packages can lead to security breaches, data loss, and damage to your project's reputation. It is crucial to regularly audit and update dependencies.
