Malicious Code Injection in nokire-arhani10 Package: A Threat to npm Users

nokire-arhani10 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-162319: Malicious code in nokire-arhani10 (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 Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The nokire-arhani10 package is part of a series of malicious packages that emerged during the tea.xyz token reward campaign. These packages are designed to manipulate the npm registry by automatically generating and publishing derivative packages. The primary functionality of these packages is to inflate developer reputation scores for token rewards, but they pose significant risks to users and the integrity of the npm ecosystem.

Vulnerability Detail

The vulnerability in the nokire-arhani10 package stems from its malicious code, which 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 that pollute the npm registry. The origin of this vulnerability is linked to the tea.xyz token reward campaign, which exploits npm's publishing mechanisms to gain undue advantages in reputation scoring.

How To Fix

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

npm uninstall nokire-arhani10

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 workaround, you can manually delete the nokire-arhani10 package from your project by running the command: npm uninstall nokire-arhani10. Additionally, consider using tools like Vulert to monitor your package-lock.json for vulnerabilities in real-time.

Conclusion

The nokire-arhani10 package presents a significant threat to npm users due to its malicious code designed to manipulate the npm registry. Immediate action is required to remove this package and safeguard your projects. Utilizing tools like Vulert can enhance your ability to monitor for vulnerabilities effectively.

See every vulnerability recorded for nokire-arhani10 →

Share this vulnerability

FAQ

The nokire-arhani10 package is a malicious npm package that is part of a campaign to inflate developer reputation scores through automated publishing of derivative packages.

This vulnerability can lead to the pollution of the npm registry, potentially compromising the integrity of your project and exposing it to further security risks.

You should immediately uninstall the nokire-arhani10 package and monitor your project for any other malicious packages.

Yes, Vulert can monitor your package-lock.json for vulnerabilities in real-time, helping you stay informed about any potential threats.

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

How To Fix

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

npm uninstall nokire-arhani10

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