Malicious Code Injection in nokire-arhani47: A Threat to npm Users
Summary
MAL-2025-162360: Malicious code in nokire-arhani47 (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-arhani47' is part of a series of malicious npm packages linked to the tea.xyz token reward campaign. These packages are designed to manipulate the npm registry by generating and publishing numerous derivative packages with randomized names. This behavior aims to inflate developer reputation scores for token rewards, compromising the integrity of the npm ecosystem.
Vulnerability Detail
The vulnerability in 'nokire-arhani47' stems from its malicious payload that modifies the package.json file by removing private flags, altering version numbers, and generating random package names. This results in the continuous republishing of variants, which pollutes the npm registry and can lead to security risks for developers who unknowingly integrate these packages into their projects.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall nokire-arhani47
If 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, avoid using the 'nokire-arhani47' package and consider using alternative packages that provide similar functionality without the associated risks. Regularly audit your project's dependencies using tools like npm audit to identify and mitigate vulnerabilities.
Conclusion
The 'nokire-arhani47' package poses a significant threat to npm users due to its malicious behavior of modifying package files and republishing variants. It is essential to remove this package and regularly audit your dependencies to maintain a secure development environment.
See every vulnerability recorded for nokire-arhani47 →
FAQ
The primary risk is that it modifies package.json files and repopulates the npm registry with malicious variants, which can lead to security vulnerabilities in applications that depend on these packages.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software using just package-lock.json. Visit Vulert Scanner to check if your application is affected without any signup.
Immediately uninstall the package using 'npm uninstall nokire-arhani47' and review your project's dependencies for any other potentially malicious packages.
Yes, tools like npm audit and Vulert can help identify vulnerabilities in your npm packages and provide recommendations for remediation.
Remove any identified malicious packages immediately and update your dependencies to secure versions. Regularly audit your project to prevent future vulnerabilities.