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

nokire-arhani24 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-162335: Malicious code in nokire-arhani24 (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 MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

The package 'nokire-arhani24' 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 that aims to exploit the npm registry by flooding it with derivative packages. These packages are designed to inflate developer reputation scores through automated publishing scripts, which can lead to significant security risks for users and developers relying on npm packages.

Vulnerability Detail

The vulnerability in 'nokire-arhani24' originates from its association with the tea.xyz token reward campaign. The malicious code within this package modifies the package.json file by removing private flags, altering version numbers, and generating random package names. This behavior not only pollutes the npm registry but also poses a risk of unintentional dependency on compromised packages, potentially leading to further exploitation and security breaches.

How To Fix

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

npm uninstall nokire-arhani24

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 manually check your package-lock.json file for any references to 'nokire-arhani24' and remove it. Additionally, consider using tools like Vulert to monitor your dependencies for vulnerabilities. You can access the Vulert playground at https://vulert.com/scanner to check if your application is affected by this vulnerability without any signup.

Conclusion

The 'nokire-arhani24' package poses a significant threat due to its malicious code designed to exploit the npm registry. It is crucial for developers to remain vigilant, regularly update their dependencies, and utilize tools like Vulert to monitor for vulnerabilities. By taking proactive measures, you can safeguard your projects against potential security risks.

See every vulnerability recorded for nokire-arhani24 →

Share this vulnerability

FAQ

The 'nokire-arhani24' package is an npm package that has been identified as part of a malicious campaign to exploit the npm registry.

The malicious code modifies your package.json file, potentially leading to the publication of compromised packages and security vulnerabilities in your project.

You should remove the 'nokire-arhani24' package from your project and check for any other affected packages.

Yes, you can use Vulert to monitor your dependencies for vulnerabilities in real-time by analyzing your package-lock.json file.

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

How To Fix

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

npm uninstall nokire-arhani24

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