Malicious Code Injection in mobile_dolphin_0xrequest Package

mobile_dolphin_0xrequest Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-105920: Malicious code in mobile_dolphin_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 mobile_dolphin_0xrequest package is part of the npm ecosystem, typically used for various mobile development tasks. However, it has been identified as part of a malicious campaign that exploits npm's package publishing system. This package is designed to inflate developer reputation scores through the automatic generation and publication of derivative packages with randomized names.

Vulnerability Detail

The vulnerability originates from the package being associated with the tea.xyz token reward campaign, which floods the npm registry with malicious packages. These packages contain scripts that modify the package.json file to remove private flags, change version numbers, and generate random package names. The continuous republishing of these variants can lead to pollution of the npm registry, making it difficult for developers to find legitimate packages and potentially compromising their applications.

How To Fix

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

npm uninstall mobile_dolphin_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, avoid using the mobile_dolphin_0xrequest package and monitor your project for any dependencies that may indirectly include it. Regularly check your package-lock.json file for any signs of this package and remove it if found.

Conclusion

The mobile_dolphin_0xrequest package poses a significant risk due to its association with malicious activities aimed at manipulating the npm registry. Developers are advised to uninstall this package and monitor their projects for any related vulnerabilities. Utilizing tools like Vulert can help in maintaining the security of your applications.

See every vulnerability recorded for mobile_dolphin_0xrequest →

Share this vulnerability

FAQ

It is an npm package that has been identified as part of a malicious campaign to inflate developer reputation scores.

The vulnerability can lead to the pollution of the npm registry, making it difficult to find legitimate packages and potentially compromising your application's security.

You should uninstall the package immediately using the command: npm uninstall mobile_dolphin_0xrequest.

Yes, you can use Vulert, which monitors and alerts in real-time for open-source vulnerabilities using your package-lock.json file. You can check your application for vulnerabilities without signing up at the Vulert playground.

Currently, there is no patched version available. It is recommended to remove the package until a secure version is released.

How To Fix

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

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