Malicious Code Injection in nokire-arhani64 Package - npm Vulnerability

nokire-arhani64 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-162379: Malicious code in nokire-arhani64 (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 Penetration testing for web, API and mobile 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-arhani64 package is part of the npm ecosystem, which is widely used for JavaScript package management. This package has been identified as part of a malicious campaign associated with the tea.xyz token reward initiative. It is designed to manipulate the npm registry by generating and publishing numerous derivative packages with altered names and metadata, ultimately aimed at inflating developer reputation scores.

Vulnerability Detail

The vulnerability in the nokire-arhani64 package 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 these variants, which pollutes the npm registry and can compromise the integrity of the ecosystem. The source of this vulnerability has been traced back to a campaign that exploits npm's publishing mechanisms for fraudulent purposes.

How To Fix

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

npm uninstall nokire-arhani64

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, avoid using the nokire-arhani64 package and consider using alternative packages that provide similar functionality without the associated risks. You can also implement strict dependency management practices to minimize exposure to malicious packages.

Conclusion

The nokire-arhani64 package poses a significant risk due to its malicious code that manipulates the npm registry. It is essential to remove this package from your projects and adopt best practices for dependency management to safeguard your applications from similar threats.

See every vulnerability recorded for nokire-arhani64 →

Share this vulnerability

FAQ

The nokire-arhani64 package is an npm package that has been identified as part of a malicious campaign aimed at inflating developer reputation scores through fraudulent publishing practices.

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

You can use Vulert to monitor your package-lock.json file for vulnerabilities. The Vulert playground allows you to check your application for vulnerabilities without requiring any signup.

If you have installed the nokire-arhani64 package, you should uninstall it immediately using the command 'npm uninstall nokire-arhani64' and review your dependencies for any other potentially malicious packages.

Yes, you can prevent future vulnerabilities by regularly auditing your dependencies, using tools like Vulert for real-time monitoring, and being cautious about the packages you include in your projects.

How To Fix

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

npm uninstall nokire-arhani64

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