Malicious Code Injection in nokire-arjuna39: A Threat to npm Ecosystem
Summary
MAL-2025-162451: Malicious code in nokire-arjuna39 (npm). Affected versions are not published. No fix is published. How to fix ↓
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.
No signup required · Results in about 60 seconds
Background
The package 'nokire-arjuna39' is part of a series of npm packages that emerged during the tea.xyz token reward campaign. These packages are designed to inflate developer reputation scores by automatically generating and publishing derivative packages with randomized names. The malicious nature of this package lies in its ability to modify the package.json file, remove private flags, and continuously republish variants, thereby polluting the npm registry.
Vulnerability Detail
The vulnerability in 'nokire-arjuna39' originates from its association with the tea.xyz token reward campaign, which employs autopublish scripts to create and publish numerous derivative packages. This malicious behavior includes altering the package.json file to remove private flags and changing version numbers, which can lead to unauthorized access and misuse of the npm registry. The continuous republishing of these variants can significantly disrupt the integrity of the npm ecosystem, making it difficult for developers to trust the packages they use.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall nokire-arjuna39
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 package from being used in your project by removing it from your package.json file and running 'npm uninstall nokire-arjuna39'. Additionally, consider using tools like Vulert to monitor your project for vulnerabilities. You can check if your application is affected by this vulnerability using the Vulert playground at https://vulert.com/scanner without any signup.
Conclusion
The 'nokire-arjuna39' package poses a significant threat to the npm ecosystem due to its malicious code that modifies package.json and repopulates the npm registry with harmful variants. It is crucial for developers to remain vigilant and utilize tools like Vulert to monitor their projects for vulnerabilities. Immediate action should be taken to remove this package and safeguard your applications.
See every vulnerability recorded for nokire-arjuna39 →
FAQ
'nokire-arjuna39' is an npm package that is part of a malicious campaign aimed at inflating developer reputation scores through the automatic generation and publication of derivative packages.
The vulnerability can lead to unauthorized modifications of your package.json file, potentially exposing your project to security risks and disrupting the integrity of the npm registry.
You should immediately uninstall the package from your project and monitor your dependencies for any other malicious packages.
Yes, regularly audit your dependencies using tools like Vulert, which can alert you to open-source vulnerabilities in real-time without requiring access to the code.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by vulnerabilities without any signup.