Malicious Code Vulnerability in nokire-arjuna19: Exploitation of npm Registry

nokire-arjuna19 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-162429: Malicious code in nokire-arjuna19 (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-arjuna19' is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to facilitate the automatic generation and publication of derivative packages, which can inflate developer reputation scores in exchange for token rewards. Its functionality includes creating random package names and modifying package metadata, making it susceptible to malicious exploitation.

Vulnerability Detail

The vulnerability in 'nokire-arjuna19' originates from its involvement in a malicious campaign that modifies the package.json file to remove private flags and change version numbers. This allows the package to continuously republish variants with randomized names, polluting the npm registry and potentially compromising the integrity of other packages. The malicious payload can lead to unauthorized access, data leaks, and a compromised development environment.

How To Fix

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

npm uninstall nokire-arjuna19

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 'nokire-arjuna19' by adding it to your project's .npmrc file with the following line: 'package-lock=false'. This will help avoid the automatic installation of this malicious package.

Conclusion

The 'nokire-arjuna19' package poses a significant risk due to its malicious code that modifies package metadata and repopulates the npm registry with harmful variants. It is crucial to remove this package and monitor for any updates to safeguard your project.

See every vulnerability recorded for nokire-arjuna19 →

Share this vulnerability

FAQ

'nokire-arjuna19' is an npm package involved in a malicious campaign that generates and publishes derivative packages to inflate developer reputation scores.

The vulnerability can lead to unauthorized modifications in your project, potentially compromising its security and integrity.

You should remove 'nokire-arjuna19' from your project and monitor for any updates or patches that may address this vulnerability.

Yes, you can use Vulert, which monitors and alerts in real-time for open-source vulnerabilities using just your package-lock.json file.

You can use the Vulert playground at Vulert Scanner to check if your application is affected without needing to sign up.

How To Fix

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

npm uninstall nokire-arjuna19

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