Malicious Code Injection in rival-poke78: A Threat to npm Ecosystem
Summary
MAL-2025-165064: Malicious code in rival-poke78 (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
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
Background
rival-poke78 is an npm package that has been identified as part of a malicious campaign targeting the npm registry. It is designed to manipulate package metadata and inflate developer reputation scores through automated publishing of derivative packages. This package's functionality is compromised due to its malicious intent, which poses a significant risk to developers and users relying on npm packages.
Vulnerability Detail
The vulnerability in rival-poke78 originates from its involvement in the tea.xyz token reward campaign, which floods the npm registry with malicious packages. The package contains scripts that automatically modify package.json files to remove private flags, change version numbers, and generate random package names. This behavior leads to the pollution of the npm registry, potentially affecting other packages and developers by inflating reputation scores fraudulently. The malicious payload can also lead to the unintentional installation of compromised packages by users unaware of the threat.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall rival-poke78If 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 rival-poke78 and any other packages that may have been published as part of the malicious campaign. Regularly audit your package.json and package-lock.json files to identify and remove any suspicious packages.
Conclusion
The discovery of malicious code in the rival-poke78 package highlights the ongoing risks associated with open-source software. It is essential for developers to remain vigilant, regularly audit their dependencies, and utilize tools like Vulert to monitor for vulnerabilities. By taking proactive measures, developers can protect their projects and contribute to a safer npm ecosystem.
See every vulnerability recorded for rival-poke78 →
FAQ
rival-poke78 is an npm package identified as part of a malicious campaign that manipulates package metadata and inflates developer reputation scores.
The vulnerability can lead to the installation of compromised packages, pollution of the npm registry, and potential security risks for your project.
You should uninstall rival-poke78 immediately using 'npm uninstall rival-poke78' and audit your dependencies for any other malicious packages.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software using just package-lock.json. You can check your application for vulnerabilities without signup at the Vulert playground.
Yes, tools like Vulert can help you monitor your dependencies for vulnerabilities in real-time, ensuring your project remains secure.
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
