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

nokire-arhani18 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-162328: Malicious code in nokire-arhani18 (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-arhani18' is part of the npm ecosystem, which is widely used for JavaScript package management. It is often utilized in various applications to manage dependencies and streamline development processes. However, this package has been identified as part of a malicious campaign that aims to exploit npm's publishing mechanisms, leading to potential security risks for developers and users alike.

Vulnerability Detail

The vulnerability in 'nokire-arhani18' stems from its association with the tea.xyz token reward campaign, which has been flooding the npm registry with malicious packages. These packages contain scripts that automatically modify the package.json file to remove private flags, change version numbers, and generate random package names. This behavior not only inflates developer reputation scores but also pollutes the npm registry with potentially harmful variants, posing a significant risk to users who may unknowingly install these compromised packages.

How To Fix

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

npm uninstall nokire-arhani18

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 avoid using 'nokire-arhani18' and any other packages that may be associated with the tea.xyz campaign. Instead, look for alternative packages that provide similar functionality without the associated risks. Always verify the source and reputation of packages before installation.

Conclusion

The 'nokire-arhani18' package poses a significant security threat due to its malicious code that alters package.json files and floods the npm registry with harmful variants. It is essential for developers to remove this package and remain vigilant about the dependencies they use in their projects.

See every vulnerability recorded for nokire-arhani18 →

Share this vulnerability

FAQ

The main risk is that it modifies package.json files to remove security flags and publishes malicious variants, which can compromise the integrity of your application.

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

You should uninstall the package immediately using 'npm uninstall nokire-arhani18' and review your project's dependencies for any other potentially malicious packages.

No, there are currently no patches available for this package, and it is recommended to remove it from your project.

Regularly audit your dependencies, use trusted sources for packages, and consider employing 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-arhani18

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