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

nokire-arjuna21 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-162432: Malicious code in nokire-arjuna21 (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-arjuna21' is part of a malicious campaign targeting npm users, primarily associated with the tea.xyz token reward scheme. 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 centered around automating the publication process, which poses significant risks to the integrity of the npm ecosystem.

Vulnerability Detail

The vulnerability in 'nokire-arjuna21' originates from its malicious design, which includes scripts that modify the package.json file to remove private flags, alter version numbers, and generate random package names. This behavior leads to the continuous republishing of variants, polluting the npm registry and potentially compromising the security of projects that depend on this package. The ramifications include the risk of dependency confusion, reputation damage for developers, and the potential for malicious code execution in dependent applications.

How To Fix

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

npm uninstall nokire-arjuna21

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-arjuna21' package and any packages that depend on it. Regularly audit your package dependencies using tools like npm audit to identify and mitigate vulnerabilities.

Conclusion

The 'nokire-arjuna21' package poses a significant threat to npm users due to its malicious design aimed at manipulating the npm registry. Immediate action is required to remove this package and safeguard your projects from potential vulnerabilities. Regular monitoring and auditing of dependencies are essential to maintain security.

See every vulnerability recorded for nokire-arjuna21 →

Share this vulnerability

FAQ

'nokire-arjuna21' is an npm package involved in a malicious campaign that automates the publication of derivative packages to inflate developer reputation scores.

The vulnerability can lead to dependency confusion, potential execution of malicious code, and pollution of the npm registry, which can compromise the integrity of your project.

You should immediately uninstall the package using 'npm uninstall nokire-arjuna21' and audit your dependencies for any other vulnerabilities.

Currently, there is no patched version available for 'nokire-arjuna21'. The best course of action is to remove the package entirely.

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

How To Fix

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

npm uninstall nokire-arjuna21

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