Malicious Code Injection in rival-poke4 Package - npm Vulnerability

rival-poke4 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-165022: Malicious code in rival-poke4 (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-poke4 package is part of the npm ecosystem, primarily used for various JavaScript applications. It is often leveraged by developers to enhance functionality within their projects. However, this package has been identified as part of a malicious campaign that aims to exploit npm's publishing mechanisms, leading to significant security concerns.

Vulnerability Detail

The vulnerability originates from the rival-poke4 package being associated with the tea.xyz token reward campaign, which has flooded the npm registry with malicious packages. These packages contain scripts that automatically modify the package.json file to remove private flags, alter version numbers, and generate random package names. This behavior not only inflates developer reputation scores but also pollutes the npm registry, potentially leading to the installation of compromised packages by unsuspecting developers.

How To Fix

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

npm uninstall rival-poke4

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-poke4 package and look for alternative packages that provide similar functionality without the associated risks. Additionally, ensure that your package-lock.json is monitored for any unauthorized changes.

Conclusion

The rival-poke4 package poses a significant security risk due to its malicious code designed to exploit npm's publishing system. It is essential to remove this package from your projects and monitor for any unauthorized changes. Utilizing tools like Vulert can help maintain the security of your applications.

See every vulnerability recorded for rival-poke4 →

Share this vulnerability

FAQ

The rival-poke4 package is an npm package used in JavaScript applications, but it has been compromised with malicious code.

This vulnerability can lead to the installation of malicious packages, compromising your application's integrity and security.

You should uninstall the rival-poke4 package immediately and monitor your project for any unauthorized changes.

Yes, you can use Vulert, which monitors and alerts for open-source vulnerabilities in your software using just package-lock.json.

You can use the Vulert playground at Vulert Scanner to check if your application is affected without any signup.

How To Fix

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

npm uninstall rival-poke4

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