Malicious Code Injection in rival-poke1: A Threat to npm Users

rival-poke1 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-164977: Malicious code in rival-poke1 (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 Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The 'rival-poke1' package is part of the npm ecosystem, which is widely used for JavaScript package management. This package is associated with the tea.xyz token reward campaign, which has been linked to a series of malicious activities aimed at inflating developer reputation scores. The package's functionality has been compromised, making it a vector for malicious code that can affect users and developers alike.

Vulnerability Detail

The vulnerability in 'rival-poke1' originates from its involvement in a malicious campaign that floods the npm registry with derivative packages. This package contains scripts designed to automatically modify the package.json file by removing private flags, changing version numbers, and generating random package names. The continuous republishing of these variants can pollute the npm registry, leading to potential security risks for users who may unknowingly install these compromised packages.

How To Fix

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

npm uninstall rival-poke1

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 avoid using the 'rival-poke1' package until a fix is confirmed. Additionally, you can manually check your package.json file for any unauthorized changes and revert them if necessary.

Conclusion

The 'rival-poke1' package poses a significant security risk due to its malicious code that alters package configurations and floods the npm registry. Users are advised to update or remove the package and utilize tools like Vulert to monitor for vulnerabilities in their applications.

See every vulnerability recorded for rival-poke1 →

Share this vulnerability

FAQ

The vulnerability involves malicious code that modifies package.json files and floods the npm registry with compromised packages.

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

If you have installed rival-poke1, it is crucial to update the package immediately or remove it from your project to prevent potential security risks.

While specific exploits have not been detailed, the nature of the vulnerability allows for unauthorized modifications and potential security breaches.

Regularly update your dependencies, use tools like Vulert for monitoring, and audit your packages for known vulnerabilities.

How To Fix

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

npm uninstall rival-poke1

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