Malicious Code Injection in Judicial Bass 0xRequest Package

judicial_bass_0xrequest Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-104718: Malicious code in judicial_bass_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 MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

The judicial_bass_0xrequest package is part of the npm ecosystem, often associated with token reward campaigns. It is designed to facilitate interactions with various APIs and services. However, this package has been identified as malicious, containing scripts that manipulate package metadata and publish unauthorized variants to inflate developer reputation scores.

Vulnerability Detail

The vulnerability originates from the package's association with the tea.xyz token reward campaign, which has been known to flood the npm registry with malicious packages. The malicious code modifies the package.json file to remove private flags, alters version numbers, and generates random package names, leading to the continuous republishing of these variants. This not only compromises the integrity of the npm registry but also poses risks to developers who may unknowingly use these tainted packages.

How To Fix

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

npm uninstall judicial_bass_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 measure, avoid using the judicial_bass_0xrequest package and look for alternative packages that provide similar functionality without the associated risks. Additionally, you can monitor your package dependencies using tools like Vulert, which can alert you to vulnerabilities in real-time.

Conclusion

The judicial_bass_0xrequest package has been identified as a malicious entity within the npm ecosystem, posing significant risks to developers. It is essential to uninstall this package and monitor your dependencies for vulnerabilities. Utilizing tools like Vulert can aid in maintaining the security of your projects.

See every vulnerability recorded for judicial_bass_0xrequest →

Share this vulnerability

FAQ

It is an npm package associated with token reward campaigns, designed for API interactions but has been compromised with malicious code.

The malicious code modifies your package.json, potentially leading to unauthorized package republishing and compromising your project's integrity.

You should uninstall the package immediately and monitor your project for any unauthorized changes or dependencies.

Yes, tools like Vulert can help monitor your package dependencies for vulnerabilities in real-time without requiring code access.

You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.

How To Fix

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

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