Malicious Code Injection in rival-poke80 Package

rival-poke80 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-165067: Malicious code in rival-poke80 (npm). Affected versions are not published. No fix is published. How to fix ↓

Free scan

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.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

The rival-poke80 package is part of the npm ecosystem, commonly used for various JavaScript applications. It is intended to facilitate certain functionalities within the npm environment. However, this package has been identified as part of a malicious campaign that exploits npm's publishing capabilities, leading to significant security risks for developers and users alike.

Vulnerability Detail

The vulnerability in the rival-poke80 package stems from its involvement in a malicious campaign that generates and publishes derivative packages with randomized names. This is achieved through scripts that modify the package.json file to remove private flags, alter version numbers, and continuously republish variants. The malicious payload can lead to pollution of the npm registry, inflate developer reputation scores fraudulently, and potentially introduce harmful code into dependent applications.

How To Fix

This package is malicious. Remove it and rotate any credentials it could have accessed.

npm uninstall rival-poke80

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 remove the rival-poke80 package from your project by executing the following command: npm uninstall rival-poke80. Additionally, consider using alternative packages that do not have known vulnerabilities.

Conclusion

The rival-poke80 package has been identified as a vector for malicious code injection, posing significant risks to developers and users. It is essential to take proactive measures, such as updating or removing the package and utilizing tools like Vulert for ongoing monitoring of vulnerabilities.

See every vulnerability recorded for rival-poke80 →

Share this vulnerability

FAQ

The vulnerability involves malicious code that modifies package.json to remove private flags and republish variants, leading to potential security risks.

You can use Vulert to monitor and alert for open-source vulnerabilities in your software. Visit Vulert Scanner to check your application without needing to sign up.

Using the rival-poke80 package can lead to the introduction of malicious code into your application, potentially compromising security and functionality.

Regularly updating packages, using tools like Vulert for monitoring vulnerabilities, and auditing dependencies can help prevent similar issues.

If immediate updates are not possible, consider removing the package and using alternatives until a secure version is available.

How To Fix

This package is malicious. Remove it and rotate any credentials it could have accessed.

npm uninstall rival-poke80

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 →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback