Malicious Code Injection in nokire-arhani91: A Threat to npm Ecosystem
Summary
MAL-2025-162409: Malicious code in nokire-arhani91 (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-arhani91' is part of a broader campaign targeting the npm ecosystem, specifically linked to the tea.xyz token reward initiative. This package is designed to manipulate the npm registry by generating and publishing derivative packages with randomized names. Its functionality is primarily focused on inflating developer reputation scores to earn token rewards, which poses significant risks to the integrity of the npm registry.
Vulnerability Detail
The vulnerability in 'nokire-arhani91' stems from its malicious code that 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. This behavior not only pollutes the npm registry but also compromises the security of applications relying on these packages, potentially leading to unauthorized access or data breaches.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall nokire-arhani91If 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-arhani91' package and replace it with a trusted alternative. Additionally, you can monitor your package-lock.json file for any unauthorized changes, ensuring that no malicious packages are introduced.
Conclusion
The 'nokire-arhani91' package poses a significant threat to the npm ecosystem due to its malicious code designed to manipulate the npm registry. It is crucial for developers to remove this package and monitor their dependencies to ensure the security of their applications.
See every vulnerability recorded for nokire-arhani91 →
FAQ
The primary risk is the potential for unauthorized access and data breaches due to the malicious modifications made to the package.json file.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Simply upload your package-lock.json file to the Vulert playground at Vulert Scanner to check for vulnerabilities.
Regularly auditing your dependencies and using tools like Vulert can help identify and mitigate vulnerabilities before they affect your application.
Remove any identified malicious packages immediately and replace them with trusted alternatives. Ensure to update your dependencies accordingly.
Yes, you should report any malicious packages to npm to help protect the community and prevent further exploitation.
