Malicious Code Injection in nokire-arhani32: A Threat to npm Ecosystem
Summary
MAL-2025-162344: Malicious code in nokire-arhani32 (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-arhani32' is part of a malicious campaign that exploits the npm ecosystem. It is designed to automate the generation and publication of derivative packages, which can inflate developer reputation scores for token rewards. This package, like others in the campaign, contains scripts that manipulate package metadata and publish numerous variants to the npm registry, leading to pollution of the ecosystem.
Vulnerability Detail
The vulnerability in 'nokire-arhani32' originates from its involvement in the tea.xyz token reward scheme, which aims to exploit npm's publishing capabilities. The malicious code modifies the package.json file by removing private flags, altering version numbers, and generating random package names. This behavior can lead to a compromised npm registry, where developers may unknowingly install malicious packages, risking their applications and systems.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall nokire-arhani32If 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 workaround, you can avoid using the 'nokire-arhani32' package altogether and look for alternative packages that provide similar functionality without the associated risks. Additionally, regularly audit your npm packages using tools like 'npm audit' to identify and mitigate vulnerabilities.
Conclusion
The 'nokire-arhani32' package poses a significant threat to the npm ecosystem due to its malicious behavior. It is crucial for developers to be vigilant, regularly audit their dependencies, and utilize tools like Vulert to ensure their applications remain secure. Immediate action is required to remove this package and mitigate any potential risks.
See every vulnerability recorded for nokire-arhani32 →
FAQ
The main issue is that it contains malicious code that modifies package metadata and floods the npm registry with derivative packages, potentially compromising the integrity of the ecosystem.
You can use the Vulert platform to monitor and alert for open-source vulnerabilities in your software. Visit Vulert Scanner to check if your application is affected without requiring any signup.
You should uninstall the package immediately using 'npm uninstall nokire-arhani32' and check your package-lock.json for any references to it.
While specific alternatives depend on the functionality you need, consider searching the npm registry for reputable packages that serve similar purposes without the associated risks.
Regularly audit your dependencies using tools like 'npm audit', keep your packages updated, and monitor for vulnerabilities using services like Vulert.
