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

nokire-zenitsu255 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-163612: Malicious code in nokire-zenitsu255 (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 Devnack Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The package 'nokire-zenitsu255' is part of a broader campaign associated with the tea.xyz token reward system, which has been known to flood the npm registry with malicious packages. These packages are designed to inflate developer reputation scores by automatically generating and publishing numerous derivative packages with randomized names. The functionality of this package is compromised due to its malicious intent, posing a significant risk to developers and users relying on npm for package management.

Vulnerability Detail

The vulnerability stems from the presence of malicious code within the 'nokire-zenitsu255' package. This code modifies the package.json file to remove private flags, alters version numbers, and generates random package names, effectively polluting the npm registry. The malicious payload is part of a larger scheme to manipulate the npm ecosystem for token rewards, leading to potential security risks for developers who may unknowingly use these compromised packages.

How To Fix

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

npm uninstall nokire-zenitsu255

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-zenitsu255' package and look for alternative packages that provide similar functionality without the associated risks. Additionally, you can monitor your project for any unintended dependencies that may include this malicious package.

Conclusion

The 'nokire-zenitsu255' package poses a significant threat to the npm ecosystem due to its malicious code designed to manipulate the package registry. It is crucial for developers to remove this package from their projects and monitor for any dependencies that may inadvertently include it. Utilizing tools like Vulert can help in identifying and managing such vulnerabilities effectively.

See every vulnerability recorded for nokire-zenitsu255 →

Share this vulnerability

FAQ

The 'nokire-zenitsu255' package is a malicious npm package associated with a token reward campaign that aims to inflate developer reputation scores.

The malicious code modifies your package.json file, removes private flags, and generates random package names, which can lead to security vulnerabilities and clutter in the npm registry.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software. You can check if your application is affected by visiting the Vulert playground at Vulert Scanner without any signup.

If you have installed 'nokire-zenitsu255', you should uninstall it immediately using 'npm uninstall nokire-zenitsu255' and check for any dependencies that may be affected.

Yes, you should look for alternative packages that provide similar functionality but do not have the associated risks of malicious code.

How To Fix

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

npm uninstall nokire-zenitsu255

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