Malicious Code Injection in nokire-arhani33: A Threat to npm Packages
Summary
MAL-2025-162345: Malicious code in nokire-arhani33 (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-arhani33' is part of the npm ecosystem, which is widely used for JavaScript package management. This package is associated with the tea.xyz token reward campaign, which has been known to flood the npm registry with malicious packages. The primary function of such packages is to manipulate developer reputation scores by generating and publishing numerous derivative packages with randomized names.
Vulnerability Detail
The vulnerability in 'nokire-arhani33' originates from its design to include malicious code that modifies the package.json file. This code removes private flags, alters version numbers, and generates random package names, leading to the continuous republishing of these variants. The ramifications include pollution of the npm registry, potential security risks for developers using these packages, and a compromised reputation system within the npm ecosystem.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall nokire-arhani33If 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 measure, you can avoid using the 'nokire-arhani33' package and look for alternative packages that provide similar functionality without the associated risks. Additionally, you can use the following command to uninstall the package: npm uninstall nokire-arhani33.
Conclusion
The 'nokire-arhani33' package poses a significant threat due to its malicious code designed to manipulate npm's package management system. It is crucial for developers to be aware of such vulnerabilities and take proactive measures to secure their applications by removing affected packages and utilizing monitoring tools like Vulert.
See every vulnerability recorded for nokire-arhani33 →
FAQ
The main issue is that it contains malicious code that modifies package.json files and floods the npm registry with derivative packages.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check your application without any signup.
You should uninstall the package immediately and look for alternatives to avoid potential security risks.
Yes, using this package can lead to security vulnerabilities, pollution of the npm registry, and damage to your project's reputation.
Regularly monitor your dependencies using tools like Vulert and keep your packages updated to the latest versions to mitigate risks.
