Malicious Code Injection in nokire-arhani511: A Threat to npm Ecosystem
Summary
MAL-2025-162365: Malicious code in nokire-arhani511 (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-arhani511' is part of the npm ecosystem, which is widely used for JavaScript package management. It is associated with the tea.xyz token reward campaign, which has been known to flood the npm registry with malicious packages. This package, like others in the campaign, is designed to manipulate package metadata and publish derivative packages, thereby inflating developer reputation scores for token rewards.
Vulnerability Detail
The vulnerability in 'nokire-arhani511' stems from its malicious code that modifies the package.json file by removing private flags and altering version numbers. It generates random package names, primarily themed around Indonesian culture, and continuously republishes these variants to pollute the npm registry. This behavior not only compromises the integrity of the npm ecosystem but also poses risks to developers who may unknowingly install these malicious packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall nokire-arhani511If 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-arhani511' package and replace it with a trusted alternative. Additionally, regularly audit your npm packages using 'npm audit' to identify and mitigate vulnerabilities.
Conclusion
The 'nokire-arhani511' package poses a significant threat to the npm ecosystem due to its malicious behavior. It is crucial for developers to be vigilant, remove any affected packages, and utilize tools like Vulert to monitor for vulnerabilities in their projects.
See every vulnerability recorded for nokire-arhani511 →
FAQ
The main issue is that it contains malicious code that alters package metadata and floods the npm registry with derivative packages.
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 uninstall the package immediately using 'npm uninstall nokire-arhani511' and check your package-lock.json for any references.
Yes, consider using well-established packages that serve similar functionalities without the associated risks.
It compromises the integrity of your development environment by introducing potentially harmful code and could lead to reputation damage if malicious packages are published under your name.
