Malicious Code Injection in nokire-zenitsu33: A Threat to npm Users
Summary
MAL-2025-163621: Malicious code in nokire-zenitsu33 (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-zenitsu33' is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to automate the generation and publication of derivative packages, which can inflate developer reputation scores for token rewards. However, it has been identified as containing malicious code that modifies package configurations and floods the npm registry with unwanted variants.
Vulnerability Detail
The vulnerability in 'nokire-zenitsu33' originates from its malicious payload, which alters the package.json file by removing private flags, changing version numbers, and generating random package names. This behavior leads to the continuous republishing of these variants, polluting the npm registry and potentially compromising the integrity of other packages. The malicious scripts included (auto.js, autopublish.js, etc.) are designed to automate this process, making it difficult for developers to track and manage their dependencies effectively.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall nokire-zenitsu33If 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-zenitsu33' package and replace it with a trusted alternative. Always verify the integrity and source of packages before including them in your project.
Conclusion
The 'nokire-zenitsu33' package poses a significant risk due to its malicious behavior, which can compromise the integrity of the npm registry and affect developers' projects. It is essential to remove this package and monitor your dependencies to ensure ongoing security.
See every vulnerability recorded for nokire-zenitsu33 →
FAQ
The main issue is that it contains malicious code that modifies package configurations and floods the npm registry with unwanted variants.
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 needing to sign up.
You should uninstall the package immediately using 'npm uninstall nokire-zenitsu33' and review your other dependencies for security.
Yes, consider using well-established and trusted packages that serve similar functionalities without the associated risks.
Regularly audit your dependencies, use tools like Vulert for monitoring, and only install packages from reputable sources.
