Malicious Code Injection in nokire-arhani57: A Threat to npm Ecosystem
Summary
MAL-2025-162371: Malicious code in nokire-arhani57 (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-arhani57' is part of a series of malicious npm packages associated with the tea.xyz token reward campaign. These packages are designed to manipulate the npm registry by automatically generating and publishing derivative packages with randomized names. This behavior aims to inflate developer reputation scores for rewards in the tea protocol, making it a significant threat to the integrity of the npm ecosystem.
Vulnerability Detail
The vulnerability in 'nokire-arhani57' originates from its malicious payload, which modifies the package.json file to remove private flags and alters version numbers. It generates random package names, often themed around Indonesian culture, and continuously republishes these variants to pollute the npm registry. This can lead to a compromised development environment, where developers may unknowingly use these malicious packages, exposing their applications to further risks.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall nokire-arhani57If 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 use the following command to prevent the installation of this malicious package: 'npm install --no-optional'. However, the best approach is to completely remove the package as mentioned above.
Conclusion
The 'nokire-arhani57' package poses a serious threat to the npm ecosystem due to its malicious behavior. It is crucial for developers to be vigilant and regularly check their dependencies for vulnerabilities. By removing this package and utilizing tools like Vulert, developers can safeguard their applications from potential threats.
See every vulnerability recorded for nokire-arhani57 →
FAQ
The primary risk is that it modifies your package.json file and introduces potentially harmful code into your project, which can lead to security vulnerabilities.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software. Visit Vulert Scanner to check your application without any signup.
You should immediately uninstall the package using 'npm uninstall nokire-arhani57' and check your project for any other malicious packages.
Yes, tools like Vulert can help you monitor your dependencies for vulnerabilities in real-time.
It is advisable to check for vulnerabilities regularly, especially after adding new packages or updating existing ones.
