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

rival-poke49 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-165032: Malicious code in rival-poke49 (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

The rival-poke49 package is part of the npm ecosystem, which is widely used for JavaScript package management. This package, like many others, is intended to facilitate the development of applications by providing reusable code. However, it has been identified as part of a malicious campaign that aims to exploit the npm registry by generating and publishing numerous derivative packages with altered metadata. This behavior not only affects the integrity of the npm ecosystem but also poses a risk to developers who may unknowingly use these compromised packages.

Vulnerability Detail

The vulnerability in the rival-poke49 package stems from its association with a malicious campaign that modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This results in the continuous republishing of these variants, which can lead to pollution of the npm registry and inflate developer reputation scores fraudulently. The malicious payload is designed to execute autopublish scripts that automate this process, making it difficult for developers to identify and avoid these compromised packages.

How To Fix

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

npm uninstall rival-poke49

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-poke49 package and look for alternative packages that provide similar functionality without the associated risks. Always verify the integrity and reputation of packages before installation.

Conclusion

The rival-poke49 package poses a significant risk to developers within the npm ecosystem due to its malicious behavior aimed at manipulating the npm registry. It is essential to take immediate action by uninstalling this package and monitoring your projects for vulnerabilities to maintain security and integrity.

See every vulnerability recorded for rival-poke49 →

Share this vulnerability

FAQ

The rival-poke49 package is an npm package that has been identified as part of a malicious campaign aimed at exploiting the npm registry.

Using the rival-poke49 package can lead to the introduction of malicious code into your project, compromising its security and integrity.

You should uninstall the rival-poke49 package immediately using the command npm uninstall rival-poke49.

You can use tools like Vulert, which monitors your package-lock.json file to alert you in real-time for open-source vulnerabilities.

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

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