Malicious Code Injection in nokire-arhani5: A Threat to npm Users
Summary
MAL-2025-162363: Malicious code in nokire-arhani5 (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-arhani5' is part of the npm ecosystem, which is widely used for JavaScript package management. This package is associated with the tea.xyz token reward campaign, which has been known to flood the npm registry with malicious packages. The primary functionality of such packages is to generate and publish derivative packages automatically, often with the intent of inflating developer reputation scores for token rewards. This behavior poses significant risks to developers and users relying on npm for secure package management.
Vulnerability Detail
The vulnerability in 'nokire-arhani5' originates from its design to include malicious payloads that modify the package.json file. This includes removing private flags, altering version numbers, and generating random package names, which can lead to the pollution of the npm registry. The malicious scripts (auto.js, autopublish.js, etc.) continuously republish these variants, making it difficult for users to identify legitimate packages. The ramifications of this vulnerability include compromised security for applications using these packages, potential data breaches, and a general degradation 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-arhani5If 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 avoid using the 'nokire-arhani5' package and look for alternative packages that provide similar functionality without the associated risks. Additionally, consider using tools like Vulert to monitor your package-lock.json for vulnerabilities.
Conclusion
The 'nokire-arhani5' package poses a significant security threat to npm users due to its malicious code and automated publishing behavior. It is essential to remove this package from your projects and monitor for vulnerabilities using tools like Vulert to maintain the integrity of your applications.
See every vulnerability recorded for nokire-arhani5 →
FAQ
'nokire-arhani5' is an npm package associated with a malicious campaign that aims to inflate developer reputation scores through automated publishing of derivative packages.
The vulnerability can lead to the inclusion of malicious code in your application, potentially compromising security and data integrity.
You should uninstall the package immediately using 'npm uninstall nokire-arhani5' and check for any other affected packages in your project.
You can use 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.
Yes, tools like Vulert can help you monitor and alert for vulnerabilities in your npm packages without requiring access to your code or installation.
