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

nokire-arhani26 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-162337: Malicious code in nokire-arhani26 (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 MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

The package 'nokire-arhani26' is part of a broader campaign targeting the npm ecosystem, specifically related to the tea.xyz token reward initiative. This package is designed to manipulate the npm registry by generating and publishing numerous derivative packages with randomized names. Its primary function is to inflate developer reputation scores for token rewards, which poses a significant risk to the integrity of the npm ecosystem.

Vulnerability Detail

The vulnerability in 'nokire-arhani26' stems from its malicious code that modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior leads to the continuous republishing of variants, which pollutes the npm registry and compromises the security and reliability of the ecosystem. The origin of this vulnerability is linked to the tea.xyz token reward campaign, which employs autopublish scripts to automate the creation of these malicious packages.

How To Fix

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

npm uninstall nokire-arhani26

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 measure, you can avoid using 'nokire-arhani26' and any packages that depend on it. Additionally, consider using npm audit to identify and address vulnerabilities in your project dependencies.

Conclusion

The 'nokire-arhani26' package poses a significant threat to the npm ecosystem due to its malicious behavior aimed at inflating developer reputation scores. It is essential to remove this package and monitor your dependencies for vulnerabilities to maintain the integrity of your projects.

See every vulnerability recorded for nokire-arhani26 →

Share this vulnerability

FAQ

'nokire-arhani26' is an npm package associated with a malicious campaign that aims to inflate developer reputation scores through the automatic generation of derivative packages.

The vulnerability can lead to the pollution of the npm registry, potentially compromising the security and reliability of your project by introducing malicious code.

You should immediately remove the package from your project and check for any dependencies that may have been affected. Use npm audit to identify vulnerabilities.

Yes, you can use tools like Vulert, which monitors your package-lock.json for open-source vulnerabilities in real-time without requiring code access or installation.

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

How To Fix

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

npm uninstall nokire-arhani26

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