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

rival-poke9 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-165077: Malicious code in rival-poke9 (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 Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

rival-poke9 is an npm package that has been identified as part of a malicious campaign targeting the npm registry. This package is designed to exploit the npm ecosystem by generating and publishing derivative packages with randomized names. Its primary function is to inflate developer reputation scores through the tea.xyz token reward campaign, which has led to the proliferation of malicious packages within the registry.

Vulnerability Detail

The vulnerability in rival-poke9 stems from its inclusion in a malicious campaign that modifies the package.json file to remove private flags and change version numbers. It generates random package names, often themed around Indonesian culture, and continuously republishes variants to pollute the npm registry. This behavior not only compromises the integrity of the npm ecosystem but also poses risks to developers who may unknowingly install these malicious packages, leading to potential data breaches or system compromises.

How To Fix

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

npm uninstall rival-poke9

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, avoid using rival-poke9 and any other packages that may be part of the tea.xyz token reward campaign. Regularly audit your project's dependencies using tools like npm audit to identify and mitigate potential vulnerabilities.

Conclusion

The rival-poke9 package poses a significant threat to the npm ecosystem due to its malicious behavior of modifying package metadata and republishing variants. It is crucial for developers to remain vigilant, regularly audit their dependencies, and utilize tools like Vulert to monitor for vulnerabilities. Taking proactive steps to remove affected packages and update dependencies will help safeguard your projects.

See every vulnerability recorded for rival-poke9 →

Share this vulnerability

FAQ

rival-poke9 is an npm package that has been identified as part of a malicious campaign aimed at inflating developer reputation scores through the creation of derivative packages.

The vulnerability can lead to the installation of malicious code, which may compromise your project's security and integrity, potentially leading to data breaches.

You can use Vulert, a tool that monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check your application without requiring any installation.

If you have installed rival-poke9, you should uninstall it immediately using 'npm uninstall rival-poke9' and audit your dependencies for any other vulnerabilities.

Yes, tools like npm audit and Vulert can help you identify and manage vulnerabilities in your project's dependencies effectively.

How To Fix

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

npm uninstall rival-poke9

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