Malicious Code Injection in rival-poke102: A Threat to npm Ecosystem
Summary
MAL-2025-164981: Malicious code in rival-poke102 (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
rival-poke102 is an npm package that appears to be part of a broader malicious campaign targeting the npm registry. This package is designed to manipulate developer reputation scores through the automatic generation and publication of derivative packages. The malicious nature of this package lies in its ability to alter package metadata and continuously republish variants, contributing to the pollution of the npm ecosystem.
Vulnerability Detail
The vulnerability in rival-poke102 originates from its inclusion in a campaign that floods the npm registry with malicious packages. It contains scripts that modify the package.json file to remove private flags, change version numbers, and generate random package names. This behavior not only compromises the integrity of the npm registry but also poses a risk to developers who may unknowingly use these compromised packages, leading to potential security breaches and loss of reputation.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall rival-poke102If 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 rival-poke102 and any other packages that may be part of the malicious campaign. Regularly audit your package-lock.json file and remove any suspicious packages. You can also use tools like Vulert to monitor your dependencies for vulnerabilities.
Conclusion
The rival-poke102 package poses a significant threat to the npm ecosystem due to its malicious behavior of modifying package metadata and republishing variants. It is essential for developers to remain vigilant, regularly audit their dependencies, and utilize tools like Vulert to ensure their projects are secure from such vulnerabilities.
See every vulnerability recorded for rival-poke102 →
FAQ
rival-poke102 is an npm package involved in a malicious campaign that aims to inflate developer reputation scores by flooding the npm registry with derivative packages.
The vulnerability can lead to the inclusion of malicious code in your project, potentially compromising security and affecting the integrity of your application.
You should immediately remove the rival-poke102 package from your project and audit your dependencies for any other malicious packages.
Yes, you can use Vulert to monitor your project for open-source vulnerabilities in real-time. It requires only your package-lock.json file to provide alerts.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.
