Malicious Code Injection in nokire-zenitsu37: A Threat to npm Ecosystem
Summary
MAL-2025-163625: Malicious code in nokire-zenitsu37 (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-zenitsu37' 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 often contain scripts designed to manipulate package metadata and inflate developer reputation scores for token rewards, posing a significant risk to developers and users alike.
Vulnerability Detail
The vulnerability in 'nokire-zenitsu37' stems from its malicious code that modifies the package.json file by removing private flags and changing version numbers. It generates random package names, primarily themed around Indonesian culture, and continuously republishes these variants to pollute the npm registry. This behavior can lead to reputation inflation for malicious actors and compromise the integrity of the npm ecosystem.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall nokire-zenitsu37If 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-zenitsu37' package and monitor your project for any dependencies that may inadvertently include it. Use the following command to check for vulnerabilities in your project: 'npm audit'.
Conclusion
The 'nokire-zenitsu37' package poses a significant threat due to its malicious code that alters package metadata and floods the npm registry. It is crucial for developers to remove this package and monitor their projects for vulnerabilities to maintain the integrity of their applications.
See every vulnerability recorded for nokire-zenitsu37 →
FAQ
The primary risk is that it modifies package metadata and floods the npm registry with malicious variants, which can compromise the integrity of the ecosystem.
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 requiring any signup.
You should immediately uninstall the package using 'npm uninstall nokire-zenitsu37' and check your project for any other affected dependencies.
Currently, there are no patched versions available. It is recommended to remove the package entirely.
Regularly audit your dependencies using 'npm audit', keep your packages updated, and consider using tools like Vulert for real-time monitoring.
