Malicious Code Vulnerability in nokire-arhani76: Exploitation of npm Packages for Reputation Inflation
Summary
MAL-2025-162392: Malicious code in nokire-arhani76 (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-arhani76' is part of the npm ecosystem and appears to be associated with the tea.xyz token reward campaign. This campaign has been known to flood the npm registry with numerous packages that contain scripts designed to manipulate package metadata. The primary functionality of these packages is to generate and publish derivative packages with randomized names, aimed at inflating developer reputation scores for token rewards.
Vulnerability Detail
The vulnerability in 'nokire-arhani76' stems from its malicious payload, which modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior not only compromises the integrity of the npm registry but also poses a risk to developers who may unknowingly use these compromised packages. The malicious scripts (auto.js, autopublish.js, etc.) continuously republish variants, polluting the npm ecosystem and potentially leading to further exploitation.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall nokire-arhani76If 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-arhani76' package and look for alternative packages that provide similar functionality without the associated risks. Always verify the integrity of packages before installation.
Conclusion
The 'nokire-arhani76' package poses a significant risk due to its malicious behavior aimed at manipulating the npm registry. It is crucial for developers to remain vigilant, regularly check for vulnerabilities, and utilize tools like Vulert to ensure the integrity of their applications.
See every vulnerability recorded for nokire-arhani76 →
FAQ
The primary risk is the modification of package.json files, which can lead to the installation of compromised packages and pollution of the npm registry.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. By uploading your package-lock.json file, you can check for vulnerabilities without needing to access the code.
You should uninstall the package immediately using 'npm uninstall nokire-arhani76' and look for alternative packages.
Yes, tools like Vulert can help monitor your npm packages for vulnerabilities in real-time. You can also use the Vulert playground to check your application without signing up.
Signs of a potentially malicious package include unusual modifications to package.json, frequent republishing of variants, and lack of documentation or community support.
