Malicious Code Injection in nokire-zenitsu32: A Threat to npm Ecosystem
Summary
MAL-2025-163620: Malicious code in nokire-zenitsu32 (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-zenitsu32' is part of a series of npm packages that emerged during the tea.xyz token reward campaign. These packages are designed to manipulate npm's publishing system, often containing scripts that automatically generate and publish derivative packages. This behavior is aimed at inflating developer reputation scores for token rewards, which poses a significant risk to the integrity of the npm registry.
Vulnerability Detail
The vulnerability in 'nokire-zenitsu32' stems from its inclusion in a malicious campaign that employs autopublish scripts to modify package.json files. These scripts remove private flags, alter version numbers, and generate random package names, leading to the continuous republishing of variants that pollute the npm registry. This not only compromises the security of the affected package but also affects the broader npm ecosystem by creating confusion and potential conflicts among legitimate packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall nokire-zenitsu32If 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 measure, you can prevent the installation of the malicious package by using npm's package-lock.json to monitor your dependencies. Ensure that your project does not include 'nokire-zenitsu32' in its dependencies. You can also use the following command to audit your project for vulnerabilities: npm audit.
Conclusion
The 'nokire-zenitsu32' package poses a significant risk due to its malicious behavior aimed at manipulating the npm registry. It is crucial for developers to be vigilant about their dependencies and to take immediate action to remove any affected packages. Utilizing tools like Vulert can aid in monitoring and securing your projects against such vulnerabilities.
See every vulnerability recorded for nokire-zenitsu32 →
FAQ
'nokire-zenitsu32' is an npm package that has been identified as part of a malicious campaign aimed at manipulating the npm registry.
The vulnerability can lead to the installation of malicious code, which may compromise your project's security and integrity.
You should immediately remove 'nokire-zenitsu32' from your project and audit your dependencies for any other vulnerabilities.
You can use tools like Vulert, which monitors your package-lock.json for open-source vulnerabilities in real-time without requiring code access or installation.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without signing up.
