Malicious Code Injection in final_wolverine_0xrequest Package

final_wolverine_0xrequest Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-102712: Malicious code in final_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 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 final_wolverine_0xrequest package is part of the npm ecosystem, which is widely used for JavaScript development. It is designed to facilitate requests in applications but has been compromised as part of a malicious campaign. This package has been associated with the tea.xyz token reward campaign, which aims to inflate developer reputation scores through the automatic generation and publication of derivative packages.

Vulnerability Detail

The vulnerability in the final_wolverine_0xrequest package stems from its malicious code that modifies the package.json file. This code removes private flags, alters version numbers, and generates random package names, leading to the pollution of the npm registry. The malicious payload is part of a broader scheme to exploit npm's publishing capabilities, potentially affecting developers' projects by introducing unwanted dependencies and compromising their applications.

How To Fix

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

npm uninstall final_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 final_wolverine_0xrequest package and look for alternative packages that provide similar functionality without the associated risks.

Conclusion

The final_wolverine_0xrequest package has been identified as containing malicious code that can compromise your application. It is essential to remove this package and monitor your dependencies for vulnerabilities using tools like Vulert. Staying informed and proactive can help protect your projects from such threats.

See every vulnerability recorded for final_wolverine_0xrequest →

Share this vulnerability

FAQ

It is an npm package designed for making requests in JavaScript applications, but it has been compromised with malicious code.

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

You should uninstall the final_wolverine_0xrequest package immediately and look for alternatives.

Currently, there is no patched version available. It is recommended to uninstall the package until a safe version is released.

The malicious code can lead to unwanted changes in your package.json file, potentially introducing security risks and instability in your application.

How To Fix

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

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