Malicious Code Injection in nokire-arhani43: A Threat to npm Packages
Summary
MAL-2025-162356: Malicious code in nokire-arhani43 (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-arhani43' is part of a series of npm packages associated with the tea.xyz token reward campaign. These packages are designed to manipulate the npm registry by automatically generating and publishing numerous derivative packages with randomized names. This behavior is intended to inflate developer reputation scores for rewards in the tea protocol, making it a significant concern for developers relying on npm for package management.
Vulnerability Detail
The vulnerability in 'nokire-arhani43' originates from its malicious payload, which alters the package.json file by removing private flags and changing version numbers. It generates random package names, often themed around Indonesian culture, and continuously republishes these variants, leading to pollution of the npm registry. This not only compromises the integrity of the npm ecosystem but also poses risks to developers who may unknowingly use these tainted packages in their projects.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall nokire-arhani43If 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-arhani43' package and any other packages associated with the tea.xyz campaign. Monitor your package-lock.json file for any unauthorized changes and consider using tools like Vulert to track vulnerabilities in your dependencies.
Conclusion
The 'nokire-arhani43' package poses a significant threat due to its malicious code that alters package metadata and floods the npm registry with compromised packages. Developers should take immediate action to remove this package and utilize tools like Vulert to monitor their projects for vulnerabilities. Staying proactive in dependency management is essential for maintaining software security.
See every vulnerability recorded for nokire-arhani43 →
FAQ
The primary risk is that it modifies your package.json file and publishes malicious variants, which can compromise your project's integrity and security.
You can use Vulert, which monitors your package-lock.json for vulnerabilities in real-time. Visit the Vulert playground at Vulert Scanner to check your application without any signup.
Immediately uninstall the package using 'npm uninstall nokire-arhani43' and review your project for any other potentially compromised dependencies.
Yes, tools like Vulert can help you monitor and alert you in real-time for open-source vulnerabilities in your software.
Regularly update your dependencies, use trusted sources for packages, and employ vulnerability scanning tools like Vulert to stay informed about potential threats.
