Malicious Code Injection in nokire-zenitsu35: A Threat to npm Packages
Summary
MAL-2025-163623: Malicious code in nokire-zenitsu35 (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-zenitsu35' 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 typically contain scripts that automate the generation and publication of derivative packages, thereby inflating developer reputation scores for token rewards. The presence of such malicious packages poses a significant risk to developers and users relying on npm for secure package management.
Vulnerability Detail
The vulnerability in 'nokire-zenitsu35' originates from its design to include autopublish scripts that modify the package.json file. These modifications remove private flags, change version numbers, and generate random package names, leading to the continuous republishing of variants that pollute the npm registry. This behavior can result in compromised security for applications using these packages, as they may inadvertently include malicious code in their dependencies.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall nokire-zenitsu35If 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-zenitsu35' package and instead look for alternative packages that provide similar functionality without the associated risks. Always review the packages you include in your project for any signs of malicious behavior.
Conclusion
The 'nokire-zenitsu35' package presents a significant security risk due to its malicious code designed to manipulate npm package publishing. It is crucial for developers to remove this package from their projects and to remain vigilant about the packages they use. Utilizing tools like Vulert can help in monitoring for such vulnerabilities effectively.
See every vulnerability recorded for nokire-zenitsu35 →
FAQ
The 'nokire-zenitsu35' package is an npm package that has been identified as malicious, part of a campaign to inflate developer reputation scores through automated publishing.
This vulnerability can lead to the inclusion of malicious code in your application, potentially compromising its security and integrity.
You should uninstall the package immediately using 'npm uninstall nokire-zenitsu35' and check your application for any other affected dependencies.
You can use tools like Vulert, which monitors your package-lock.json file for open-source vulnerabilities in real-time. You can also check your application using the Vulert playground without any signup.
Yes, you should look for alternative packages that provide similar functionality but are known to be secure and free from malicious code.
