Malicious Code Injection in rival-poke1: A Threat to npm Users
Summary
MAL-2025-164977: Malicious code in rival-poke1 (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 'rival-poke1' package 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 linked to a series of malicious activities aimed at inflating developer reputation scores. The package's functionality has been compromised, making it a vector for malicious code that can affect users and developers alike.
Vulnerability Detail
The vulnerability in 'rival-poke1' originates from its involvement in a malicious campaign that floods the npm registry with derivative packages. This package contains scripts designed to automatically modify the package.json file by removing private flags, changing version numbers, and generating random package names. The continuous republishing of these variants can pollute the npm registry, leading to potential security risks for users who may unknowingly install these compromised packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall rival-poke1
If 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 'rival-poke1' package until a fix is confirmed. Additionally, you can manually check your package.json file for any unauthorized changes and revert them if necessary.
Conclusion
The 'rival-poke1' package poses a significant security risk due to its malicious code that alters package configurations and floods the npm registry. Users are advised to update or remove the package and utilize tools like Vulert to monitor for vulnerabilities in their applications.
See every vulnerability recorded for rival-poke1 →
FAQ
The vulnerability involves malicious code that modifies package.json files and floods the npm registry with compromised packages.
You can use Vulert, which monitors open-source vulnerabilities in real-time. Visit Vulert Scanner to check if your application is affected without any signup.
If you have installed rival-poke1, it is crucial to update the package immediately or remove it from your project to prevent potential security risks.
While specific exploits have not been detailed, the nature of the vulnerability allows for unauthorized modifications and potential security breaches.
Regularly update your dependencies, use tools like Vulert for monitoring, and audit your packages for known vulnerabilities.