Malicious Code Injection in convinced_wolf_0xrequest Package

convinced_wolf_0xrequest Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-100979: Malicious code in convinced_wolf_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 Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The convinced_wolf_0xrequest package is part of a series of npm packages that have been associated with the tea.xyz token reward campaign. These packages are designed to automate the publication of derivative packages with randomized names, which can inflate developer reputation scores in exchange for token rewards. However, this functionality has been exploited to introduce malicious code that compromises the integrity of the npm registry.

Vulnerability Detail

The vulnerability originates from the malicious intent behind the convinced_wolf_0xrequest package, which modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior leads to the continuous republishing of variants that pollute the npm registry, potentially affecting developers and users who rely on the integrity of npm packages. The malicious payload can compromise the security of applications that depend on this package, leading to unauthorized access or data breaches.

How To Fix

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

npm uninstall convinced_wolf_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 convinced_wolf_0xrequest package and look for alternative packages that provide similar functionality without the associated risks. Additionally, ensure that your package-lock.json file is monitored for vulnerabilities using tools like Vulert, which can alert you to open-source vulnerabilities in real-time.

Conclusion

The convinced_wolf_0xrequest package poses a significant security risk due to its malicious code that modifies package configurations and repopulates the npm registry with compromised packages. It is crucial to remove this package and utilize monitoring tools like Vulert to safeguard your applications against such vulnerabilities.

See every vulnerability recorded for convinced_wolf_0xrequest →

Share this vulnerability

FAQ

It is an npm package that has been linked to a malicious campaign aimed at inflating developer reputation scores through automated publishing.

The vulnerability can lead to unauthorized modifications in your application's dependencies, potentially compromising its security and integrity.

You should uninstall the convinced_wolf_0xrequest package immediately and monitor your project for any other vulnerabilities.

Yes, tools like Vulert can monitor your package-lock.json file and alert you to any open-source vulnerabilities in real-time.

Absolutely! 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 convinced_wolf_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