Malicious Code Injection in nokire-zenitsu22: A Threat to npm Packages
Summary
MAL-2025-163609: Malicious code in nokire-zenitsu22 (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
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
Background
The package 'nokire-zenitsu22' is part of the npm ecosystem, which is widely used for JavaScript package management. This package has been identified as part of a malicious campaign that aims to exploit the npm registry by flooding it with derivative packages. These packages are designed to inflate developer reputation scores through automated publishing scripts, leading to potential security risks for users and developers alike.
Vulnerability Detail
The vulnerability in 'nokire-zenitsu22' stems from its involvement in a malicious campaign that modifies the package.json file to remove private flags and change version numbers. It generates random package names and continuously republishes variants, which pollutes the npm registry. This behavior can lead to unintentional installations of malicious packages, compromising the security of applications that depend on them.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall nokire-zenitsu22If 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-zenitsu22' package and check your package-lock.json file for any dependencies that may include it. If found, remove those dependencies and replace them with trusted alternatives.
Conclusion
The 'nokire-zenitsu22' package poses a significant security risk due to its malicious code that modifies package files and floods the npm registry. It is essential for developers to be vigilant about their dependencies and utilize tools like Vulert to monitor for vulnerabilities. Immediate action should be taken to remove this package and any associated risks.
See every vulnerability recorded for nokire-zenitsu22 →
FAQ
The main risk is that it can introduce malicious code into your application, potentially leading to data breaches or other security vulnerabilities.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. By using the Vulert playground, you can check if your application is affected without any signup.
You should uninstall the package immediately using 'npm uninstall nokire-zenitsu22' and review your dependencies for any other potentially malicious packages.
Yes, tools like Vulert can help you monitor your dependencies for vulnerabilities in real-time, making it easier to maintain secure applications.
Signs of compromise may include unexpected behavior, performance issues, or unauthorized access to sensitive data. Regularly auditing your dependencies can help identify potential issues.
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
