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

nokire-arhani92 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-162410: Malicious code in nokire-arhani92 (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-arhani92' 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. These packages are designed to manipulate developer reputation scores by automatically generating and publishing derivative packages with random names.

Vulnerability Detail

The vulnerability in 'nokire-arhani92' 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 is intended to inflate developer reputation scores and pollute the npm registry with numerous variants of the package. The origin of this vulnerability is linked to the tea.xyz token reward campaign, which exploits npm's publishing mechanisms to distribute harmful code.

How To Fix

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

npm uninstall nokire-arhani92

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 prevent the installation of the 'nokire-arhani92' package by adding it to your project's .npmignore file or by using npm's package-lock.json to monitor dependencies. However, the best approach is to remove the package entirely.

Conclusion

The 'nokire-arhani92' package poses a significant threat due to its malicious code designed to manipulate npm's publishing system. It is crucial for developers to remain vigilant, regularly update their dependencies, and utilize tools like Vulert to monitor for vulnerabilities. Immediate action should be taken to remove this package from any affected projects.

See every vulnerability recorded for nokire-arhani92 →

Share this vulnerability

FAQ

The 'nokire-arhani92' package is an npm package that has been identified as malicious, associated with a campaign to inflate developer reputation scores.

This vulnerability can lead to the pollution of your project's dependencies, potentially introducing harmful code and affecting the integrity of your application.

If you have installed 'nokire-arhani92', you should immediately uninstall it using 'npm uninstall nokire-arhani92' and review your project's dependencies for any other malicious packages.

You can use tools like Vulert, which monitors your package-lock.json file to alert you in real-time for open-source vulnerabilities. You can also check your application against vulnerabilities using the Vulert playground without any signup.

Yes, there are several automated tools available, including Vulert, which can help you monitor and alert for vulnerabilities in your open-source dependencies.

How To Fix

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

npm uninstall nokire-arhani92

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