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

nokire-arhani34 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-162346: Malicious code in nokire-arhani34 (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-arhani34' is part of the npm ecosystem, which is widely used for JavaScript package management. It is often utilized by developers to share and manage code libraries. However, this package has been identified as part of a malicious campaign that aims to exploit the npm registry by flooding it with derivative packages, thereby manipulating developer reputation scores for token rewards.

Vulnerability Detail

The vulnerability in 'nokire-arhani34' originates from its association with the tea.xyz token reward campaign. This package contains scripts designed to automatically generate and publish numerous derivative packages with randomized names. The malicious payload modifies the package.json file by removing private flags, altering version numbers, and continuously republishing variants, which pollutes the npm registry. This can lead to significant security risks, including the potential for dependency confusion and the introduction of further malicious code into projects that rely on these packages.

How To Fix

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

npm uninstall nokire-arhani34

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-arhani34' package and replace it with a known, secure alternative. Always review the packages you are adding to your project and check their integrity.

Conclusion

The 'nokire-arhani34' package poses a significant threat to the npm ecosystem due to its malicious code designed to manipulate the registry. It is essential for developers to be vigilant about the packages they use and to take immediate action to remove any identified vulnerabilities.

See every vulnerability recorded for nokire-arhani34 →

Share this vulnerability

FAQ

The main issue is that it contains malicious code that modifies package.json and floods the npm registry with derivative packages.

You can use Vulert, which monitors open-source vulnerabilities in your software. Visit Vulert Scanner to check your application without needing to sign up.

You should uninstall the package immediately using 'npm uninstall nokire-arhani34' and review your project's dependencies for any other potentially malicious packages.

Yes, using this package can lead to dependency confusion, security vulnerabilities, and the introduction of further malicious code into your project.

Regularly audit your dependencies, use tools like Vulert for monitoring, and only install packages from trusted sources.

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

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