Malicious Code Injection in nokire-zenitsu47: A Threat to npm Packages
Summary
MAL-2025-163636: Malicious code in nokire-zenitsu47 (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-zenitsu47' is part of the npm ecosystem, which is widely used for JavaScript package management. It is designed to facilitate the development and sharing of JavaScript code. However, this package has been identified as part of a malicious campaign that aims to inflate developer reputation scores through the automatic generation and publication of derivative packages. This vulnerability poses a significant risk to developers and users relying on npm for secure package management.
Vulnerability Detail
The vulnerability in 'nokire-zenitsu47' originates from its association with the tea.xyz token reward campaign. The package contains malicious scripts that modify the package.json file by removing private flags, changing version numbers, and generating random package names. This behavior leads to the continuous republishing of variants, polluting the npm registry and potentially compromising the integrity of other packages. The ramifications include the risk of developers unknowingly using compromised packages, which can lead to security breaches and loss of trust in the npm ecosystem.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall nokire-zenitsu47If 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-zenitsu47' package and replace it with a trusted alternative. Always verify the integrity and source of packages before installation.
Conclusion
The discovery of malicious code in the nokire-zenitsu47 package highlights the importance of vigilance in package management. Developers should take immediate action to remove affected packages and adopt best practices for dependency management to safeguard their applications.
See every vulnerability recorded for nokire-zenitsu47 →
FAQ
The main issue is that it contains malicious code that modifies package.json files and floods the npm registry with derivative packages.
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 any signup.
If you have installed nokire-zenitsu47, you should uninstall it immediately using 'npm uninstall nokire-zenitsu47' and review your dependencies for any other potentially compromised packages.
Yes, consider using trusted packages that provide similar functionality but have a verified reputation in the npm ecosystem.
To prevent future vulnerabilities, regularly audit your dependencies, use tools like Vulert for monitoring, and only install packages from reputable sources.
