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

nokire-arhani1 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-162318: Malicious code in nokire-arhani1 (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-arhani1' is part of a series of npm packages that emerged during the tea.xyz token reward campaign. These packages are designed to inflate developer reputation scores by automatically generating and publishing numerous derivative packages with randomized names. This behavior not only clutters the npm registry but also poses significant security risks to users who may unknowingly install compromised packages.

Vulnerability Detail

The vulnerability in 'nokire-arhani1' 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 is intended to continuously republish variants, polluting the npm registry and potentially leading to the installation of malicious code by unsuspecting developers. The ramifications include compromised systems, unauthorized access, and a general degradation of trust in the npm ecosystem.

How To Fix

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

npm uninstall nokire-arhani1

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-arhani1' package and instead look for alternative packages that provide similar functionality without the associated risks. Additionally, regularly audit your npm packages using tools like 'npm audit' to identify and address vulnerabilities.

Conclusion

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

See every vulnerability recorded for nokire-arhani1 →

Share this vulnerability

FAQ

The 'nokire-arhani1' package is part of a malicious campaign that aims to inflate developer reputation scores by flooding the npm registry with derivative packages.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software using just the package-lock.json file. You can also check your application against this vulnerability using the Vulert playground at Vulert Scanner.

Using compromised npm packages can lead to security breaches, unauthorized access to sensitive data, and a loss of trust in the software supply chain.

To prevent future vulnerabilities, regularly audit your dependencies, use tools like npm audit, and stay informed about known vulnerabilities in the packages you use.

If you have installed 'nokire-arhani1', immediately uninstall it using 'npm uninstall nokire-arhani1' and check for any other affected packages in your project.

How To Fix

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

npm uninstall nokire-arhani1

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