Malicious Code Vulnerability in Considerable Baboon 0xRequest Package

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-100873: Malicious code in considerable_baboon_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 Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

Background

The Considerable Baboon 0xRequest package is an npm library that is part of the tea.xyz token reward campaign. It is designed to facilitate interactions with the tea protocol, which incentivizes developers through token rewards. However, this package has been identified as containing malicious code that compromises its integrity and the security of applications that depend on it.

Vulnerability Detail

The vulnerability originates from the package being part of a larger scheme that floods the npm registry with malicious packages. It includes scripts that automatically modify the package.json file to remove private flags, change version numbers, and generate random package names. This behavior not only inflates developer reputation scores but also leads to the pollution of the npm registry, making it difficult for developers to find legitimate packages. The malicious payload can potentially allow unauthorized access to sensitive information and disrupt the functionality of applications relying on this package.

How To Fix

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

npm uninstall considerable_baboon_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 Considerable Baboon 0xRequest package altogether and look for alternative packages that provide similar functionality without the associated risks.

Conclusion

The Considerable Baboon 0xRequest package poses a significant security risk due to its malicious code. It is crucial for developers to remove this package from their projects and monitor for any potential vulnerabilities using tools like Vulert. Staying informed and proactive can help maintain the security of your applications.

See every vulnerability recorded for considerable_baboon_0xrequest →

Share this vulnerability

FAQ

It is an npm library that is part of a token reward campaign, but it has been identified to contain malicious code.

The vulnerability can lead to unauthorized access to sensitive information and disrupt the functionality of your application.

You should uninstall the package immediately using npm uninstall considerable_baboon_0xrequest.

Yes, consider using other npm packages that provide similar functionality without the security risks.

You can use Vulert, which monitors and alerts in real-time for open-source vulnerabilities using just package-lock.json. You can check if your application is affected by this vulnerability using the Vulert playground at Vulert Scanner.

Sponsored Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

How To Fix

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

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