Malicious Code Injection in nokire-arhani20: A Threat to npm Ecosystem
Summary
MAL-2025-162331: Malicious code in nokire-arhani20 (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-arhani20' 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 is intended to inflate developer reputation scores for token rewards, posing a significant risk to the integrity of the npm ecosystem.
Vulnerability Detail
The vulnerability in 'nokire-arhani20' originates from its malicious payload, which modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This allows the package to continuously republish variants, polluting the npm registry and potentially leading to the distribution of compromised software. The malicious scripts included in the package (auto.js, autopublish.js, etc.) automate this process, making it difficult for developers to identify and mitigate the threat.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall nokire-arhani20If 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-arhani20' package and any packages that depend on it. Regularly audit your npm packages using 'npm audit' to identify any vulnerabilities in your dependencies.
Conclusion
The 'nokire-arhani20' package poses a significant threat to the npm ecosystem due to its malicious behavior of modifying package files and republishing variants. It is crucial for developers to take immediate action to remove this package and monitor their dependencies for similar vulnerabilities.
See every vulnerability recorded for nokire-arhani20 →
FAQ
The main risk is that it can modify your project's package.json file and republish malicious variants, potentially leading to the distribution of compromised software.
You can use Vulert's playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring any signup.
You should uninstall the package immediately using 'npm uninstall nokire-arhani20' and check for any dependencies that may rely on it.
Yes, Vulert can monitor and alert you in real-time for open-source vulnerabilities in your software using just package-lock.json.
Regularly audit your dependencies, use tools like Vulert for monitoring, and stay updated on security advisories related to the packages you use.
