Malicious Code Injection in nokire-zenitsu49: A Threat to npm Packages

nokire-zenitsu49 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-163638: Malicious code in nokire-zenitsu49 (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-zenitsu49' is part of a series of npm packages that emerged during the tea.xyz token reward campaign. These packages are designed to automate the generation and publication of derivative packages, often with randomized names. This behavior is intended to inflate developer reputation scores in exchange for tea protocol token rewards. However, this functionality has led to significant security concerns due to the malicious code embedded within these packages.

Vulnerability Detail

The vulnerability in 'nokire-zenitsu49' originates from its malicious payload, which modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior allows the package to continuously republish variants, polluting the npm registry and potentially compromising other packages. The malicious scripts (auto.js, autopublish.js, etc.) are designed to exploit the npm ecosystem, leading to a degradation of trust and reliability in package management.

How To Fix

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

npm uninstall nokire-zenitsu49

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 'nokire-zenitsu49' and any other packages associated with the tea.xyz token reward campaign. Regularly audit your npm packages to ensure that no malicious packages are present. You can also use tools like Vulert to monitor your package-lock.json for vulnerabilities.

Conclusion

The 'nokire-zenitsu49' package poses a significant threat due to its malicious code designed to manipulate the npm registry. It is crucial for developers to be vigilant and regularly audit their dependencies to mitigate such risks. By removing this package and utilizing tools like Vulert, you can enhance the security of your projects.

See every vulnerability recorded for nokire-zenitsu49 →

Share this vulnerability

FAQ

'nokire-zenitsu49' is an npm package that is part of a malicious campaign aimed at inflating developer reputation scores through automated package publishing.

The vulnerability can lead to the pollution of the npm registry, potentially compromising the integrity of your project's dependencies and exposing it to further security risks.

You should uninstall the package immediately using the command 'npm uninstall nokire-zenitsu49' and audit your project for any other malicious packages.

Regularly audit your npm packages and use tools like Vulert to monitor for vulnerabilities in your package-lock.json. This proactive approach can help you stay informed about potential threats.

Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.

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-zenitsu49

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