Malicious Code Injection in rival_wildcat_0xrequest Package

rival_wildcat_0xrequest Updated 18 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-108162: Malicious code in rival_wildcat_0xrequest (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 rival_wildcat_0xrequest package is part of the npm ecosystem and is typically used for various web development tasks. However, it has been identified as part of a malicious campaign that exploits npm's package publishing system. This package is designed to inflate developer reputation scores through the automatic generation and publication of derivative packages, which can lead to significant security risks.

Vulnerability Detail

The vulnerability in the rival_wildcat_0xrequest package stems from its association with a malicious campaign that modifies the package.json file to remove private flags and alters version numbers. It generates random package names and continuously republishes these variants, polluting the npm registry. This behavior can lead to unauthorized access, reputation damage for developers, and potential exploitation of systems using these compromised packages.

How To Fix

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

npm uninstall rival_wildcat_0xrequest

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_wildcat_0xrequest package and replace it with a trusted alternative. Ensure that your package-lock.json file is monitored for any unauthorized changes. You can also use tools like Vulert to monitor your dependencies for vulnerabilities.

Conclusion

The rival_wildcat_0xrequest package poses a significant security risk due to its malicious code that modifies package configurations and republishes variants. It is essential to remove this package and monitor your dependencies to safeguard your application from potential threats.

See every vulnerability recorded for rival_wildcat_0xrequest →

Share this vulnerability

FAQ

It is an npm package that has been identified as part of a malicious campaign to inflate developer reputation scores through the automatic generation of derivative packages.

The vulnerability can lead to unauthorized access, reputation damage, and potential exploitation of your application through compromised packages.

You should uninstall the rival_wildcat_0xrequest package immediately and check for any other affected packages in your project.

You can use tools like Vulert, which monitors your package-lock.json file for 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.

How To Fix

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

npm uninstall rival_wildcat_0xrequest

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