Malicious Code Injection in brave_asp_0xrequest Package

brave_asp_0xrequest Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-100082: Malicious code in brave_asp_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 brave_asp_0xrequest package is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to facilitate token rewards but has been compromised to include malicious scripts that can harm developers and the integrity of the npm registry. The package's functionality is undermined by its ability to generate and publish derivative packages with altered metadata, which can lead to reputation inflation for malicious actors.

Vulnerability Detail

The vulnerability originates from the package being part of a broader malicious campaign that floods the npm registry with harmful packages. It modifies the package.json file to remove private flags, changes version numbers, and generates random package names, which can lead to pollution of the npm registry. This behavior can compromise the security of applications relying on this package and can potentially lead 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 brave_asp_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, you can prevent the use of this package by removing it from your package.json file and running npm install to update your dependencies. Additionally, consider using a tool like Vulert to monitor your project for vulnerabilities. You can check if your application is affected by this vulnerability using the Vulert playground at https://vulert.com/scanner without any signup.

Conclusion

The brave_asp_0xrequest package has been identified as containing malicious code that can compromise the integrity of applications using it. It is crucial to remove this package and monitor your dependencies for any vulnerabilities. Utilizing tools like Vulert can help maintain the security of your software.

See every vulnerability recorded for brave_asp_0xrequest →

Share this vulnerability

FAQ

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

The vulnerability can lead to unauthorized modifications in your package.json file, potentially compromising your application's security.

You should remove the brave_asp_0xrequest package from your project and monitor for any updates or patches.

Yes, Vulert allows you to monitor and alert for open-source vulnerabilities in your software using just package-lock.json.

Regularly audit your dependencies, use tools like Vulert for monitoring, and stay updated on security advisories related to your packages.

How To Fix

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

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