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

nokire-arhani80 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-162397: Malicious code in nokire-arhani80 (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 Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

The package 'nokire-arhani80' is part of a series of malicious packages that emerged during the tea.xyz token reward campaign on npm. These packages are designed to manipulate the npm registry by creating and publishing numerous derivative packages with randomized names, thereby inflating developer reputation scores for token rewards. The malicious nature of this package lies in its ability to modify essential files and continuously republish variants, leading to potential pollution of the npm registry.

Vulnerability Detail

The vulnerability in 'nokire-arhani80' originates from its design to include autopublish scripts that alter the package.json file by removing private flags and changing version numbers. This allows the package to generate random names, particularly with Indonesian themes, and republish these variants, which can lead to a significant increase in unwanted packages in the npm registry. The ramifications include a polluted registry, potential security risks for developers relying on npm, and a compromised ecosystem where malicious packages can proliferate.

How To Fix

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

npm uninstall nokire-arhani80

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

Conclusion

The 'nokire-arhani80' package poses a significant threat to the npm ecosystem by introducing malicious code that can manipulate package metadata and proliferate unwanted packages. It is crucial for developers to be vigilant, regularly audit their dependencies, and utilize tools like Vulert to monitor for vulnerabilities.

See every vulnerability recorded for nokire-arhani80 →

Share this vulnerability

FAQ

'nokire-arhani80' is a malicious npm package that is part of a campaign to inflate developer reputation scores through the creation of numerous derivative packages.

The vulnerability can lead to a polluted npm registry, making it difficult to find legitimate packages and potentially introducing security risks into your project.

You should immediately uninstall the package using 'npm uninstall nokire-arhani80' and audit your project for other vulnerabilities.

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

Yes, tools like Vulert can help identify vulnerabilities in your dependencies by analyzing your package-lock.json file.

How To Fix

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

npm uninstall nokire-arhani80

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