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

nokire-zabuza41 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-163531: Malicious code in nokire-zabuza41 (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-zabuza41' is part of a series of npm packages associated with the tea.xyz token reward campaign. These packages are designed to manipulate npm's publishing system, generating numerous derivative packages to inflate developer reputation scores for token rewards. The malicious nature of this package compromises the integrity of the npm registry.

Vulnerability Detail

The vulnerability in 'nokire-zabuza41' stems from its inclusion in a malicious campaign that employs autopublish scripts to create and publish numerous derivative packages with randomized names. This behavior not only pollutes the npm registry but also modifies the package.json file by removing private flags and altering version numbers. The potential ramifications include the degradation of the npm ecosystem's reliability and the risk of developers unknowingly using compromised packages.

How To Fix

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

npm uninstall nokire-zabuza41

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 remove the 'nokire-zabuza41' package from your project by executing the command: 'npm uninstall nokire-zabuza41'. This will prevent any malicious code from executing while you seek a safer alternative.

Conclusion

The 'nokire-zabuza41' package poses a significant threat to the npm ecosystem due to its malicious code injection capabilities. It is crucial for developers to be aware of this vulnerability, take immediate action to remove the package, and utilize tools like Vulert to monitor for future vulnerabilities.

See every vulnerability recorded for nokire-zabuza41 →

Share this vulnerability

FAQ

'nokire-zabuza41' is an npm package involved in a malicious campaign that generates numerous derivative packages to inflate developer reputation scores.

The vulnerability can lead to the introduction of malicious code into your project, potentially compromising its security and integrity.

You should uninstall the package immediately and check for any updates or patches that may address the vulnerability.

Yes, you can use Vulert, which monitors and alerts you in real-time for open-source vulnerabilities using just your package-lock.json file.

You can use the Vulert playground at Vulert Scanner to check if your application is affected without requiring any signup.

How To Fix

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

npm uninstall nokire-zabuza41

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