Malicious Code Injection in nokire-zenitsu36: A Threat to npm Packages
Summary
MAL-2025-163624: Malicious code in nokire-zenitsu36 (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-zenitsu36' is part of the npm ecosystem and appears to be associated with the tea.xyz token reward campaign. This campaign has been known to flood the npm registry with packages that contain malicious scripts designed to inflate developer reputation scores for token rewards. The package's primary functionality is compromised by its malicious intent, which involves generating and publishing derivative packages with altered metadata.
Vulnerability Detail
The vulnerability in 'nokire-zenitsu36' originates from its design to execute autopublish scripts that modify the package.json file. These modifications include removing private flags, changing version numbers, and generating random package names, which leads to the pollution of the npm registry. The ramifications of this vulnerability include potential security risks for developers who unknowingly use these packages, as well as the degradation of the npm ecosystem's integrity.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall nokire-zenitsu36If 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, avoid using the 'nokire-zenitsu36' package and consider using alternative packages that provide similar functionality without the associated risks. Always verify the integrity and reputation of packages before installation.
Conclusion
The 'nokire-zenitsu36' package poses a significant threat due to its malicious code designed to manipulate package metadata and flood the npm registry. It is essential for developers to be vigilant, regularly audit their dependencies, and utilize tools like Vulert to ensure the security of their applications.
See every vulnerability recorded for nokire-zenitsu36 →
FAQ
The primary issue is that it contains malicious code that modifies package metadata and floods the npm registry with derivative packages.
You can use Vulert to monitor and alert for open-source vulnerabilities in your software. Visit Vulert Scanner to check if your application is affected without any signup.
If you have installed nokire-zenitsu36, you should uninstall it immediately using 'npm uninstall nokire-zenitsu36' and review your dependencies for any other malicious packages.
Yes, consider using other npm packages that provide similar functionality but have a verified reputation and do not exhibit malicious behavior.
To prevent similar vulnerabilities, regularly audit your dependencies, use tools like Vulert for real-time monitoring, and only install packages from trusted sources.
