Malicious Code Injection in rival-poke86: A Threat to npm Ecosystem

rival-poke86 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-165073: Malicious code in rival-poke86 (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 Devnack Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

rival-poke86 is an npm package that has been identified as part of a malicious campaign targeting the npm registry. This package is designed to manipulate developer reputation scores through the automatic generation and publication of derivative packages. Its functionality is compromised, making it a vector for malicious activities.

Vulnerability Detail

The vulnerability in rival-poke86 originates from its association with the tea.xyz token reward campaign, which floods the npm registry with malicious packages. These packages contain scripts that modify the package.json file to remove private flags, alter version numbers, and generate random package names. The continuous republishing of these variants leads to pollution of the npm registry, potentially affecting other developers and users relying on legitimate packages.

How To Fix

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

npm uninstall rival-poke86

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, consider removing the rival-poke86 package from your project until a secure version is released. You can do this by executing the command: 'npm uninstall rival-poke86'. Additionally, monitor your package-lock.json file for any unauthorized changes.

Conclusion

The rival-poke86 package poses a significant threat due to its malicious code designed to manipulate the npm ecosystem. It is crucial for developers to take immediate action by updating or removing the package and monitoring their projects for vulnerabilities.

See every vulnerability recorded for rival-poke86 →

Share this vulnerability

FAQ

The vulnerability involves malicious code that modifies package.json files and republishes variants to inflate developer reputation scores.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check your application without any signup.

If you have installed rival-poke86, it is recommended to uninstall it immediately and monitor your project for any unauthorized changes.

Yes, the impacts include potential pollution of the npm registry and risks to other developers who may unknowingly depend on compromised packages.

Check the npm registry for any updates or patched versions of rival-poke86. If a patch is available, update the package using 'npm update rival-poke86'.

How To Fix

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

npm uninstall rival-poke86

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