Malicious Code Vulnerability in ultimate_boa_0xrequest Package

ultimate_boa_0xrequest Updated 18 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-109964: Malicious code in ultimate_boa_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 ultimate_boa_0xrequest package is part of the npm ecosystem, often used for various JavaScript applications. It has been identified as part of a larger campaign that exploits npm's publishing mechanisms. This package is particularly vulnerable due to its association with the tea.xyz token reward scheme, which has led to the proliferation of malicious packages designed to manipulate npm's registry.

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 automatically modify the package.json file to remove private flags, change version numbers, and generate random package names. This behavior can lead to the pollution of the npm registry and compromise the integrity of applications relying on this package. The malicious payload can also inflate developer reputation scores fraudulently, posing risks to the broader developer community.

How To Fix

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

npm uninstall ultimate_boa_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 prevent the installation of this package by using npm's package-lock.json file to lock down your dependencies. Ensure that your project does not include this package by regularly auditing your dependencies.

Conclusion

The ultimate_boa_0xrequest package poses a significant risk due to its association with malicious activities in the npm ecosystem. It is crucial for developers to remain vigilant, regularly audit their dependencies, and utilize tools like Vulert to ensure their applications are secure.

See every vulnerability recorded for ultimate_boa_0xrequest →

Share this vulnerability

FAQ

It is an npm package that has been identified as part of a malicious campaign targeting the npm registry.

The vulnerability can lead to the installation of malicious code, which may compromise your application's integrity and security.

Remove the package immediately and check for any updates or patches. Consider using alternative packages.

You can use tools like Vulert, which monitors your package-lock.json for vulnerabilities in real-time without requiring code access.

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 ultimate_boa_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