Malicious Code Injection in nokire-zenitsu51: A Threat to npm Ecosystem

nokire-zenitsu51 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-163641: Malicious code in nokire-zenitsu51 (npm). Affected versions are not published. No fix is published. How to fix ↓

Free scan

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.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

Background

The package 'nokire-zenitsu51' is part of a broader campaign that exploits the npm ecosystem by flooding it with malicious packages. These packages are designed to manipulate developer reputation scores through automated publishing scripts. The malicious nature of this package lies in its ability to modify essential files and continuously republish variants, thereby polluting the npm registry.

Vulnerability Detail

The vulnerability in 'nokire-zenitsu51' originates from its association with the tea.xyz token reward campaign, which aims to inflate developer reputation scores. The malicious code alters the package.json file by removing private flags, changing version numbers, and generating random package names. This not only compromises the integrity of the npm registry but also poses risks to developers who may unknowingly use these compromised packages, leading to potential security breaches in their applications.

How To Fix

This package is malicious. Remove it and rotate any credentials it could have accessed.

npm uninstall nokire-zenitsu51

If 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-zenitsu51' package and monitor your project for any other suspicious packages. Additionally, consider using tools like Vulert to monitor your package-lock.json file for vulnerabilities. You can check if your application is affected by this vulnerability using the Vulert playground at https://vulert.com/scanner without any signup.

Conclusion

The 'nokire-zenitsu51' package poses a significant threat to the npm ecosystem due to its malicious code designed to manipulate package integrity and developer reputation. It is essential to take immediate action by removing this package and monitoring your dependencies to safeguard your applications.

See every vulnerability recorded for nokire-zenitsu51 →

Share this vulnerability

FAQ

'nokire-zenitsu51' is a malicious npm package that is part of a campaign to inflate developer reputation scores through automated publishing.

This vulnerability can lead to the installation of compromised packages that may introduce security risks and affect the integrity of your application.

You should uninstall the package immediately using 'npm uninstall nokire-zenitsu51' and check for any other suspicious packages.

Regularly update your packages, monitor your dependencies using tools like Vulert, and be cautious of packages that are part of reward campaigns.

Yes, you can use Vulert, which monitors your package-lock.json file for vulnerabilities in real-time without requiring any installation.

Sponsored Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

How To Fix

This package is malicious. Remove it and rotate any credentials it could have accessed.

npm uninstall nokire-zenitsu51

If 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 →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback