Malicious Code Injection in rival-poke84: A Threat to npm Ecosystem
Summary
MAL-2025-165071: Malicious code in rival-poke84 (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 'rival-poke84' is part of a series of malicious npm packages that emerged during the tea.xyz token reward campaign. These packages are designed to manipulate the npm registry by creating and publishing numerous derivative packages with random names, thereby inflating developer reputation scores for token rewards. The malicious nature of this package poses a significant risk to developers and users relying on npm for secure package management.
Vulnerability Detail
The vulnerability in 'rival-poke84' originates from its inclusion in a malicious campaign that employs scripts to automatically generate and publish derivative packages. This results in the modification of the package.json file, removing private flags, altering version numbers, and generating random package names. The continuous republishing of these variants leads to pollution of the npm registry, which can compromise the integrity of the ecosystem and expose users to potential security risks.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall rival-poke84If 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-poke84' package and look for alternative packages that provide similar functionality without the associated risks. Always verify the source and integrity of packages before installation.
Conclusion
The 'rival-poke84' package poses a significant threat due to its malicious code designed to manipulate the npm registry. It is crucial for developers to be vigilant, regularly audit their dependencies, and utilize tools like Vulert to monitor for vulnerabilities. By taking proactive measures, the risks associated with such malicious packages can be mitigated.
See every vulnerability recorded for rival-poke84 →
FAQ
The main issue is that it contains malicious code designed to manipulate the npm registry and inflate developer reputation scores through the creation of derivative packages.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software using just the package-lock.json file. Visit the Vulert playground at Vulert Scanner to check if your application is affected.
You should uninstall the package immediately using the command 'npm uninstall rival-poke84' and review your project's dependencies for any other potentially malicious packages.
Yes, there are many reputable packages available on npm that can serve similar purposes. Always ensure to check the package's credibility and user reviews before installation.
Regularly audit your dependencies, use tools like Vulert for real-time monitoring, and only install packages from trusted sources to minimize the risk of vulnerabilities.
