Malicious Code Vulnerability in Costly Wolverine 0xRequest Package

costly_wolverine_0xrequest Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-101035: Malicious code in costly_wolverine_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 Devnack Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

The 'costly_wolverine_0xrequest' package is part of the npm ecosystem, often utilized in JavaScript projects for various functionalities. However, it has been identified as part of a malicious campaign that floods the npm registry with harmful packages. This package is designed to manipulate developer reputation scores through automated scripts that generate and publish derivative packages with altered names and properties.

Vulnerability Detail

The vulnerability stems from the package's involvement in a token reward campaign that utilizes malicious scripts to modify the package.json file. These scripts remove private flags, alter version numbers, and create random package names, leading to the pollution of the npm registry. This can result in developers unknowingly using compromised packages, which may introduce security risks and instability into their applications.

How To Fix

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

npm uninstall costly_wolverine_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 'costly_wolverine_0xrequest' package and look for alternative packages that provide similar functionality without the associated risks. Additionally, you can monitor your package-lock.json file for any unauthorized changes.

Conclusion

The 'costly_wolverine_0xrequest' package poses a significant security risk due to its malicious code designed to manipulate npm registry entries. It is crucial for developers to remove this package and monitor their projects for vulnerabilities to ensure the integrity and security of their applications.

See every vulnerability recorded for costly_wolverine_0xrequest →

Share this vulnerability

FAQ

It is an npm package that has been identified as part of a malicious campaign to manipulate developer reputation scores.

The vulnerability can lead to the introduction of malicious code into your application, potentially compromising its security and stability.

You should uninstall the package immediately and check for any dependencies that may be affected.

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

Yes, you can use the Vulert playground at Vulert Scanner to check for vulnerabilities in your application without any signup.

How To Fix

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

npm uninstall costly_wolverine_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