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

rival-poke96 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-165084: Malicious code in rival-poke96 (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 MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

The package 'rival-poke96' is part of the npm ecosystem, which is widely used for JavaScript package management. It is often utilized in various applications to enhance functionality and streamline development processes. However, this package has been identified as part of a malicious campaign that aims to inflate developer reputation scores through the generation of derivative packages with randomized names.

Vulnerability Detail

The vulnerability in 'rival-poke96' originates from its association with the tea.xyz token reward campaign. This package contains malicious scripts that modify the package.json file by removing private flags, altering version numbers, and generating random package names. The scripts continuously republish these variants, polluting the npm registry and potentially compromising the integrity of the ecosystem. The ramifications include the risk of developers unknowingly using compromised packages, which can lead to security breaches and loss of trust in the npm registry.

How To Fix

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

npm uninstall rival-poke96

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-poke96' package and instead look for alternative packages that provide similar functionality without the associated risks. Additionally, you can implement package-lock.json monitoring to detect vulnerabilities in your dependencies.

Conclusion

The 'rival-poke96' package poses a significant threat due to its malicious code that alters package configurations and repackages them. Developers should take immediate action to remove this package and monitor their projects for vulnerabilities using tools like Vulert. Staying informed and proactive is essential to maintaining the security of your applications.

See every vulnerability recorded for rival-poke96 →

Share this vulnerability

FAQ

The vulnerability involves malicious code that modifies package.json and repackages it under random names, leading to potential security risks.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Check your application against this vulnerability using the Vulert playground.

You should immediately remove the package from your project and check for any other affected packages.

While specific exploits have not been detailed, the potential for abuse exists due to the nature of the malicious scripts involved.

While many packages are safe, it is crucial to regularly monitor and audit your dependencies for vulnerabilities, as the npm ecosystem can be targeted by malicious actors.

How To Fix

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

npm uninstall rival-poke96

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