Malicious Code Injection in nokire-arhani86 Package - npm Vulnerability

nokire-arhani86 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-162403: Malicious code in nokire-arhani86 (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 nokire-arhani86 package is part of the npm ecosystem, which is widely used for JavaScript package management. This package, like many others, is intended to facilitate the development and distribution of JavaScript applications. However, it has been identified as part of a malicious campaign that aims to manipulate npm's registry by generating and publishing derivative packages with altered metadata. This vulnerability exposes developers to risks associated with compromised package integrity and potential security breaches.

Vulnerability Detail

The vulnerability in the nokire-arhani86 package stems from its association with a malicious campaign that floods the npm registry with derivative packages. These packages contain scripts designed to modify the package.json file, removing private flags and changing version numbers. The malicious payload generates random package names, often themed around Indonesian culture, and continuously republishes these variants, polluting the npm registry. This not only inflates developer reputation scores for token rewards but also poses a significant risk of introducing compromised code into applications that depend on these packages.

How To Fix

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

npm uninstall nokire-arhani86

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 prevent the installation of the nokire-arhani86 package by adding it to your project's .npmrc file with the following line: 'package-lock=false'. This will stop npm from installing any packages that are not explicitly defined in your package.json.

Conclusion

The nokire-arhani86 package presents a significant security risk due to its malicious code designed to manipulate the npm registry. It is crucial for developers to be vigilant about the packages they use, regularly update their dependencies, and utilize tools like Vulert to monitor for vulnerabilities. By taking these steps, you can help safeguard your applications from potential threats.

See every vulnerability recorded for nokire-arhani86 →

Share this vulnerability

FAQ

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

This vulnerability can lead to the introduction of compromised code into your application, potentially resulting in security breaches or instability.

If you have installed the nokire-arhani86 package, you should uninstall it immediately using 'npm uninstall nokire-arhani86' and monitor your project for any other affected packages.

You can use tools like Vulert, which monitors your package-lock.json file to alert you in real-time for open-source vulnerabilities. You can check your application against known vulnerabilities using the Vulert playground at Vulert Scanner.

To prevent similar vulnerabilities, regularly update your dependencies, use trusted sources for packages, and consider implementing automated security scanning tools in your development workflow.

How To Fix

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

npm uninstall nokire-arhani86

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