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

rival-poke94 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-165082: Malicious code in rival-poke94 (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 Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

Background

rival-poke94 is an npm package that has been associated with the tea.xyz token reward campaign. This package is designed to facilitate certain functionalities within the npm ecosystem but has been compromised to include malicious code. The vulnerability stems from the package's ability to modify its own metadata and republish itself under various names, which can lead to widespread issues in the npm registry.

Vulnerability Detail

The vulnerability in rival-poke94 originates from its malicious payload that alters the package.json file. It removes private flags, changes version numbers, and generates random package names, leading to the creation of numerous derivative packages. This behavior not only inflates developer reputation scores for the tea protocol token rewards but also pollutes the npm registry, making it difficult for developers to trust packages. The malicious scripts (auto.js, autopublish.js, etc.) are designed to automate this process, posing a significant risk to the integrity of the npm ecosystem.

How To Fix

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

npm uninstall rival-poke94

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-poke94 and monitor your package-lock.json file for any unauthorized changes. You can also use tools like Vulert to check for vulnerabilities in your dependencies without requiring code access. For example, you can visit the Vulert playground at https://vulert.com/scanner to see if your application is affected by this vulnerability.

Conclusion

The rival-poke94 package poses a significant threat due to its malicious code that alters package metadata and floods the npm registry with unauthorized packages. It is crucial for developers to uninstall this package and monitor their dependencies for vulnerabilities. Utilizing tools like Vulert can help in identifying and mitigating risks associated with open-source vulnerabilities.

See every vulnerability recorded for rival-poke94 →

Share this vulnerability

FAQ

rival-poke94 is an npm package that has been compromised to include malicious code, affecting its functionality and security.

The vulnerability can lead to unauthorized modifications of your package metadata and the proliferation of malicious packages in the npm registry, compromising your project's integrity.

You should uninstall the package immediately using npm uninstall rival-poke94 and monitor your project for any unusual behavior.

Yes, you can use Vulert's playground at Vulert Scanner to check your application for vulnerabilities without needing to sign up.

While there is currently no patched version available, it is advisable to stay updated on the package's status and remove it from your project until a fix is released.

Sponsored Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

How To Fix

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

npm uninstall rival-poke94

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