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

rival-poke55 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-165039: Malicious code in rival-poke55 (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-poke55 is a package within the npm ecosystem, often utilized for various JavaScript applications. It is part of a broader campaign that exploits npm's package management system to inflate developer reputation scores through the distribution of malicious packages. This package is particularly vulnerable due to its association with the tea.xyz token reward scheme, which has led to the proliferation of harmful scripts designed to manipulate package metadata.

Vulnerability Detail

The vulnerability in rival-poke55 stems from its malicious code, which modifies the package.json file to remove private flags and alters version numbers. This code generates random package names, often themed around Indonesian culture, and continuously republishes these variants to pollute the npm registry. The origin of this issue is linked to the tea.xyz token reward campaign, which incentivizes the creation of such malicious packages. The ramifications include potential security risks for developers who unknowingly integrate these packages into their projects, leading to compromised applications and reputational damage.

How To Fix

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

npm uninstall rival-poke55

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 rival-poke55 and any other packages associated with the tea.xyz token reward campaign. Regularly audit your package dependencies to ensure no malicious packages are present. You can also utilize tools like Vulert to monitor your package-lock.json for vulnerabilities.

Conclusion

The rival-poke55 package poses a significant threat to the npm ecosystem due to its malicious code designed to manipulate package metadata. Developers are urged to uninstall this package and monitor their dependencies for similar vulnerabilities. Utilizing tools like Vulert can help maintain the security of your applications.

See every vulnerability recorded for rival-poke55 →

Share this vulnerability

FAQ

rival-poke55 is an npm package that has been identified as containing malicious code aimed at manipulating the npm registry.

The malicious code modifies package metadata, potentially leading to security vulnerabilities and the pollution of the npm registry with harmful packages.

You should uninstall rival-poke55 immediately using the command npm uninstall rival-poke55 and check for any other affected packages.

You can use tools like Vulert, which monitors your package-lock.json for open-source vulnerabilities in real-time without requiring code access or installation.

Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.

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-poke55

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