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

nokire-arjuna60 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-162475: Malicious code in nokire-arjuna60 (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 package 'nokire-arjuna60' is part of the npm ecosystem and has been identified as a component of the tea.xyz token reward campaign. This campaign has been known to flood the npm registry with malicious packages that contain scripts designed to manipulate package metadata and inflate developer reputation scores. The primary functionality of these packages is to generate and publish derivative packages with randomized names, which can lead to significant pollution of the npm registry.

Vulnerability Detail

The vulnerability in 'nokire-arjuna60' originates from its association with malicious scripts that modify the package.json file. These scripts remove private flags, alter version numbers, and generate random package names, which can lead to the proliferation of derivative packages in the npm registry. The ramifications of this vulnerability include the potential for developers to unknowingly install compromised packages, leading to security risks and reputational damage. The technical aspects involve the use of autopublish scripts that automate the generation and publication of these malicious packages.

How To Fix

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

npm uninstall nokire-arjuna60

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 remove the 'nokire-arjuna60' package from your project by executing the command: 'npm uninstall nokire-arjuna60'. This will prevent any potential exploitation of the vulnerability until a secure version is available.

Conclusion

The 'nokire-arjuna60' package has been identified as a malicious entity within the npm ecosystem, posing significant risks to developers and their applications. It is crucial to take immediate action by updating or uninstalling the package to safeguard against potential exploitation. Utilizing tools like Vulert can further enhance your security posture by providing real-time alerts for vulnerabilities.

See every vulnerability recorded for nokire-arjuna60 →

Share this vulnerability

FAQ

The primary risk is the potential for developers to install malicious packages that can compromise their applications and inflate developer reputation scores fraudulently.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit the Vulert playground at Vulert Scanner to check if your application is affected without requiring any signup.

If you cannot update the package right away, consider uninstalling it to mitigate the risk until a secure version is released.

While specific exploits have not been publicly detailed, the nature of the vulnerability suggests that it could lead to the installation of compromised packages, which poses a significant security risk.

Regularly audit your npm packages, use tools like Vulert for real-time monitoring, and ensure that you only install packages from trusted sources.

How To Fix

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

npm uninstall nokire-arjuna60

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