Malicious Code Injection in interested_wolverine_0xrequest Package

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-104323: Malicious code in interested_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 'interested_wolverine_0xrequest' package is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to facilitate interactions with web requests, but it has been compromised to include malicious scripts that manipulate its functionality. The package's primary attributes include automatic publishing capabilities, which have been exploited to inflate developer reputation scores through the creation of numerous derivative packages.

Vulnerability Detail

The vulnerability originates from the package being part of a malicious campaign that floods the npm registry with derivative packages. These packages contain scripts that modify the package.json file to remove private flags, alter version numbers, and generate random package names. This behavior not only compromises the integrity of the package but also pollutes the npm registry, potentially leading to further exploitation by malicious actors.

How To Fix

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

npm uninstall interested_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 workaround, consider using alternative packages that provide similar functionality without the associated risks. Additionally, you can monitor your package dependencies using tools like Vulert, which analyzes your package-lock.json file to alert you of any vulnerabilities in real-time.

Conclusion

The 'interested_wolverine_0xrequest' package has been identified as containing malicious code that can compromise your application. It is crucial to remove this package and monitor your dependencies for vulnerabilities using tools like Vulert to ensure the security of your software.

See every vulnerability recorded for interested_wolverine_0xrequest →

Share this vulnerability

FAQ

It is an npm package that has been compromised to include malicious code as part of a token reward campaign.

The vulnerability can lead to unauthorized modifications of your package.json file and the proliferation of malicious packages in the npm registry.

You should remove the package immediately and consider using alternative packages that are not compromised.

Yes, you can use Vulert to monitor your package-lock.json file for vulnerabilities without needing to install any additional software.

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

How To Fix

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

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