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

nokire-arhani77 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-162393: Malicious code in nokire-arhani77 (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 Penetration testing for web, API and mobile 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-arhani77 package is part of a broader campaign targeting npm users, specifically linked to the tea.xyz token reward initiative. This package is designed to automate the generation and publication of derivative packages, which can lead to inflated developer reputation scores. Its functionality is compromised by malicious scripts that modify essential package attributes, making it a significant threat to the integrity of the npm ecosystem.

Vulnerability Detail

The vulnerability in the nokire-arhani77 package originates from its association with a malicious campaign that floods the npm registry with derivative packages. These packages contain scripts that alter the package.json file by removing private flags, changing version numbers, and generating random package names. This behavior not only pollutes the npm registry but also poses risks to developers who may unknowingly use these compromised packages, leading to potential security breaches and loss of trust in the npm ecosystem.

How To Fix

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

npm uninstall nokire-arhani77

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

Conclusion

The nokire-arhani77 package poses a significant risk to npm users due to its malicious code designed to manipulate package attributes and flood the npm registry. It is essential to remove this package and remain vigilant about the packages you use in your projects. Regular audits and updates are crucial for maintaining security.

See every vulnerability recorded for nokire-arhani77 →

Share this vulnerability

FAQ

The nokire-arhani77 package is a malicious npm package linked to a token reward campaign that automates the generation of derivative packages.

This vulnerability can lead to the injection of malicious code into your project, potentially compromising its security and integrity.

If you have installed the nokire-arhani77 package, you should uninstall it immediately using the command npm uninstall nokire-arhani77.

Regularly audit your npm packages, keep your dependencies updated, and use trusted sources for package installations.

Yes, you can use Vulert, which monitors and alerts for open-source vulnerabilities in your software using just package-lock.json. You can check your application for vulnerabilities without signup using the Vulert playground.

How To Fix

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

npm uninstall nokire-arhani77

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