Critical Malicious Code Vulnerability in dspmobile Package

dspmobile Updated 05 Feb 2026

Summary

05/02/2026
CRITICAL
No i
Critical
Not published

MAL-2026-750: Malicious code in dspmobile (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 Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The dspmobile package is a Node.js library designed for mobile application development, providing various functionalities to streamline the development process. However, it has been identified as containing malicious code, which poses a significant security risk to systems utilizing this package. Users of dspmobile should be aware of its potential vulnerabilities and the implications of using compromised software.

Vulnerability Detail

The vulnerability stems from the presence of embedded malicious code within the dspmobile package. This code can compromise any computer that has the package installed or running, leading to unauthorized access and control by external entities. The ramifications include the potential exposure of sensitive information, such as secrets and keys, which should be rotated immediately from a secure environment. The malicious nature of this code is classified under CWE-506, indicating that the product contains code that appears to be malicious.

How To Fix

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

npm uninstall dspmobile

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 workaround, if immediate removal of the package is not feasible, consider isolating the affected system from the network to prevent further unauthorized access until the package can be safely removed.

Conclusion

The dspmobile package has been identified as containing malicious code, posing serious security risks to any system that has it installed. Immediate action is required to remove the package and secure any sensitive information. Users are encouraged to utilize tools like Vulert for ongoing monitoring of vulnerabilities in their software.

See every vulnerability recorded for dspmobile →

Share this vulnerability

FAQ

dspmobile is a Node.js library used for mobile application development, offering various tools and functionalities to developers.

If you have the dspmobile package installed, your system is considered compromised. You can use Vulert to monitor and alert for vulnerabilities in your software.

Immediately rotate all secrets and keys from a different, secure computer to prevent unauthorized access.

Yes, you can use the Vulert playground to check if your application is affected by this vulnerability without requiring any installation.

CWE-506 refers to a classification of vulnerabilities where the product contains code that appears to be malicious in nature, posing significant security risks.

How To Fix

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

npm uninstall dspmobile

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