Malicious Code Injection in nokire-zenitsu30: A Threat to npm Users

nokire-zenitsu30 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-163618: Malicious code in nokire-zenitsu30 (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 Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

The package 'nokire-zenitsu30' 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. The primary function of such packages is to inflate developer reputation scores through automated publishing of derivative packages, often leading to security vulnerabilities.

Vulnerability Detail

The vulnerability in 'nokire-zenitsu30' stems from its malicious code that modifies the package.json file by removing private flags and altering 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 significant security risks, including the potential for code injection, unauthorized access, and the degradation of the npm ecosystem's integrity.

How To Fix

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

npm uninstall nokire-zenitsu30

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-zenitsu30' package and look for alternative packages that provide similar functionality without the associated risks. Always verify the integrity and reputation of packages before installation.

Conclusion

The 'nokire-zenitsu30' package poses a significant threat to npm users due to its malicious code that alters project dependencies and pollutes the npm registry. It is essential to remove this package and monitor your projects for vulnerabilities to maintain security and integrity.

See every vulnerability recorded for nokire-zenitsu30 →

Share this vulnerability

FAQ

'nokire-zenitsu30' is an npm package that has been identified as containing malicious code aimed at manipulating the npm registry.

The vulnerability can lead to unauthorized modifications of your project's dependencies, potentially introducing security risks and instability.

You should immediately uninstall the package using 'npm uninstall nokire-zenitsu30' and review your project for any other compromised packages.

You can use tools like Vulert, which monitors your package-lock.json file to alert you in real-time for open-source vulnerabilities.

Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring any signup.

How To Fix

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

npm uninstall nokire-zenitsu30

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