Malicious Code Injection in nokire-arhani72: A Threat to npm Packages

nokire-arhani72 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-162388: Malicious code in nokire-arhani72 (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-arhani72' is part of the npm ecosystem and has been identified as a malicious package linked to the tea.xyz token reward campaign. This package is designed to manipulate the npm registry by creating and publishing numerous derivative packages with randomized names, thereby inflating developer reputation scores for token rewards. Its functionality is primarily centered around automating the publishing process, which poses significant risks to the integrity of the npm ecosystem.

Vulnerability Detail

The vulnerability in 'nokire-arhani72' originates from its malicious code that modifies the package.json file to remove private flags and change version numbers. It generates random package names, primarily themed around Indonesian culture, and continuously republishes these variants to pollute the npm registry. This behavior not only compromises the security of the affected applications but also undermines the trustworthiness of the npm ecosystem as a whole.

How To Fix

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

npm uninstall nokire-arhani72

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 measure, you can prevent the installation of this malicious package by using npm's package-lock.json to monitor your dependencies. If you suspect that your project may have been affected, consider using the following command to audit your packages: 'npm audit'. This will help identify any vulnerabilities in your current dependencies.

Conclusion

The 'nokire-arhani72' package poses a significant threat to the npm ecosystem due to its malicious behavior, which includes modifying package files and publishing harmful variants. It is crucial for developers to remain vigilant, regularly audit their dependencies, and utilize tools like Vulert to ensure their applications are secure.

See every vulnerability recorded for nokire-arhani72 →

Share this vulnerability

FAQ

The main risk is that it modifies your package.json file and publishes malicious variants, which can compromise your application's security and integrity.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check your application without any signup.

You should immediately uninstall the package using 'npm uninstall nokire-arhani72' and review your other dependencies for potential vulnerabilities.

There are no patches available for the nokire-arhani72 package as it is a malicious package. The best course of action is to remove it from your project.

Regularly audit your dependencies using 'npm audit', keep your packages updated, and utilize tools like Vulert to monitor for vulnerabilities.

How To Fix

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

npm uninstall nokire-arhani72

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