Malicious Code Injection in nokire-arhani40: A Threat to npm Ecosystem
Summary
MAL-2025-162353: Malicious code in nokire-arhani40 (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-arhani40' 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. These packages often contain scripts designed to manipulate the npm registry and inflate developer reputation scores, posing a significant risk to developers and users relying on npm for secure package management.
Vulnerability Detail
The vulnerability in 'nokire-arhani40' originates from its malicious code that modifies the package.json file to remove private flags and change version numbers. It generates random package names, often themed around Indonesian culture, and continuously republishes these variants to pollute the npm registry. This behavior can lead to the proliferation of malicious packages, compromising the integrity of the npm ecosystem and potentially exposing users to security risks.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall nokire-arhani40If 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 workaround, you can monitor your project for any unauthorized changes to package.json and regularly audit your npm packages using 'npm audit'. This will help identify any vulnerabilities in your dependencies.
Conclusion
The 'nokire-arhani40' package poses a significant threat to the npm ecosystem due to its malicious code that manipulates package metadata and floods the registry with harmful variants. It is crucial for developers to take immediate action by removing the package and monitoring their dependencies to maintain the security of their applications.
See every vulnerability recorded for nokire-arhani40 →
FAQ
The main issue is that it contains malicious code designed to manipulate the npm registry and inflate developer reputation scores.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check if your application is affected without requiring any signup.
You should uninstall the package immediately using 'npm uninstall nokire-arhani40' and audit your other dependencies for vulnerabilities.
The malicious code can lead to unauthorized changes in your package.json, potentially exposing your project to further vulnerabilities and affecting its integrity.
Regularly audit your npm packages, keep them updated, and use tools like Vulert to monitor for vulnerabilities in real-time.
