Malicious Code Injection in nokire-zenitsu10: A Threat to npm Ecosystem
Summary
MAL-2025-163596: Malicious code in nokire-zenitsu10 (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-zenitsu10' is part of the npm ecosystem, which is widely used for JavaScript package management. This package, like many others, is intended to facilitate the development of applications by providing reusable code. However, it has been identified as part of a malicious campaign that aims to exploit the npm registry by generating and publishing derivative packages with harmful scripts.
Vulnerability Detail
The vulnerability in 'nokire-zenitsu10' stems from its association with a malicious campaign that floods the npm registry with derivative packages. These packages contain scripts designed to modify the package.json file by removing private flags, altering version numbers, and generating random package names. This not only inflates developer reputation scores for token rewards but also pollutes the npm registry, potentially leading to security risks for developers who unknowingly incorporate these packages into their projects.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall nokire-zenitsu10If 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 'nokire-zenitsu10' from your project by running 'npm uninstall nokire-zenitsu10'. This will prevent any malicious code from executing while you assess the situation and look for a secure alternative package.
Conclusion
The 'nokire-zenitsu10' package poses a significant risk due to its malicious code designed to manipulate the npm registry. Developers should take immediate action to update or remove the package to safeguard their projects. Utilizing tools like Vulert can help in monitoring and managing vulnerabilities effectively.
See every vulnerability recorded for nokire-zenitsu10 →
FAQ
The primary risk is the potential for malicious code execution that can alter your project's package.json and lead to the proliferation of harmful packages in the npm registry.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. By uploading your package-lock.json file to Vulert's playground, you can check for any vulnerabilities without requiring installation.
If immediate updates are not possible, consider removing the package from your project as a temporary measure to prevent any potential exploitation.
While specific exploits have not been detailed, the nature of the vulnerability suggests that it could lead to unauthorized modifications of your project and the introduction of further malicious packages.
Regularly audit your dependencies, keep your packages updated, and utilize tools like Vulert to monitor for vulnerabilities in your open-source packages.
