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

nokire-arhani99 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-162417: Malicious code in nokire-arhani99 (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 package 'nokire-arhani99' is part of a series of malicious 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 derivative packages with randomized names. The malicious nature of this package lies in its ability to manipulate the package.json file, removing private flags and altering version numbers, which can lead to a polluted npm registry and potential security risks for users.

Vulnerability Detail

The vulnerability in 'nokire-arhani99' originates from its design to execute autopublish scripts that create numerous derivative packages with random names. This behavior not only clutters the npm registry but also poses a risk of unintentional dependency on malicious packages. The payload modifies critical files, which can lead to unauthorized access or exploitation of the user's environment. The continuous republishing of these variants can also mislead developers and users into trusting compromised packages.

How To Fix

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

npm uninstall nokire-arhani99

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-arhani99' package and monitor your dependencies for any unauthorized changes. Regularly audit your npm packages using 'npm audit' to identify and address vulnerabilities.

Conclusion

The 'nokire-arhani99' package poses a significant threat to npm users due to its malicious code designed to manipulate package files and inflate developer reputation scores. It is crucial to take immediate action by uninstalling the package and monitoring your dependencies to maintain the security of your projects.

See every vulnerability recorded for nokire-arhani99 →

Share this vulnerability

FAQ

'nokire-arhani99' is a malicious npm package that is part of a campaign to inflate developer reputation scores through the automatic generation of derivative packages.

The vulnerability can lead to unauthorized modifications in your package.json file, potentially exposing your project to security risks and dependency issues.

You should uninstall the package immediately using 'npm uninstall nokire-arhani99' and audit your project for any other malicious dependencies.

Yes, you can use Vulert to monitor and alert for open-source vulnerabilities in your software. Visit Vulert Scanner to check your application without any signup.

Regularly audit your dependencies, use tools like Vulert for real-time monitoring, and stay updated with the latest security advisories for npm packages.

How To Fix

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

npm uninstall nokire-arhani99

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