Malicious Code Injection in nokire-zenitsu16: A Threat to npm Packages
Summary
MAL-2025-163602: Malicious code in nokire-zenitsu16 (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-zenitsu16' 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. The primary function of this package is to serve as a tool for developers, but it has been compromised to include harmful scripts that manipulate package metadata.
Vulnerability Detail
The vulnerability in 'nokire-zenitsu16' originates from its association with a malicious campaign that aims to inflate developer reputation scores through the automatic generation and publication of derivative packages. The malicious payload alters the package.json file by removing private flags, changing version numbers, and generating random package names. This not only pollutes the npm registry but also poses a risk to developers who may unknowingly use these compromised packages, potentially leading to security breaches in their applications.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall nokire-zenitsu16If 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-zenitsu16' package from your project by executing the command: 'npm uninstall nokire-zenitsu16'. This will prevent any malicious scripts from executing in your environment until a secure version is available.
Conclusion
The 'nokire-zenitsu16' package has been identified as containing malicious code that poses significant risks to developers and their applications. It is crucial to take immediate action by updating or uninstalling the package to safeguard your projects. Utilizing tools like Vulert can further enhance your security posture by providing real-time alerts for vulnerabilities.
See every vulnerability recorded for nokire-zenitsu16 →
FAQ
The primary risk is the injection of malicious code that can alter package metadata and lead to the proliferation of compromised packages in the npm registry.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. By analyzing your package-lock.json file, Vulert can identify if your application is affected.
If an immediate update is not possible, consider uninstalling the package as a temporary measure to mitigate risks.
Yes, tools like Vulert can help you monitor your dependencies for vulnerabilities without requiring access to your code or installation.
Detailed information can be found in the npm registry and security advisories related to the nokire-zenitsu16 package.
