Malicious Code Injection in nokire-rara85: A Threat to npm Ecosystem
Summary
MAL-2025-163378: Malicious code in nokire-rara85 (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-rara85' 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 npm with malicious packages. These packages often contain scripts designed to manipulate the npm registry and inflate developer reputation scores through the automatic generation and publication of derivative packages.
Vulnerability Detail
The vulnerability in 'nokire-rara85' stems from its malicious payload that modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior is intended to pollute the npm registry and can lead to significant security risks, including the potential for unauthorized access to sensitive data and the spread of further malicious packages. The origin of this vulnerability is linked to the tea.xyz token reward campaign, which exploits npm's publishing mechanisms.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall nokire-rara85If 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 prevent the installation of this package by adding it to your project's .npmrc file with the following line: 'package-lock=false'. This will stop npm from using the package-lock.json file, but it is not a long-term solution.
Conclusion
The 'nokire-rara85' package poses a significant threat to the npm ecosystem due to its malicious behavior. Developers are urged to remove this package from their projects and monitor their applications for vulnerabilities using tools like Vulert. Staying informed and proactive is essential to maintaining security in open-source software.
See every vulnerability recorded for nokire-rara85 →
FAQ
The main risk is that it modifies package.json to remove private flags and publishes malicious variants, which can lead to security breaches and data exposure.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check if your application is affected without requiring any signup.
You should uninstall the package immediately using 'npm uninstall nokire-rara85' and ensure your package-lock.json is updated.
Currently, there are no known patches for nokire-rara85. The best course of action is to remove the package entirely.
The campaign inflates developer reputation scores by flooding the npm registry with derivative packages, which can lead to a loss of trust in the ecosystem and potential security vulnerabilities.
