Malicious Code Detected in desktopx Package - Security Alert

desktopx Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-18330: Malicious code in desktopx (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 desktopx package is an npm library designed for creating and managing desktop applications with customizable features. It allows developers to build applications that can interact with system resources and provide a rich user experience. However, the package has been found to contain malicious code, posing significant security risks to users and their applications.

Vulnerability Detail

The vulnerability in the desktopx package originates from the inclusion of malicious code that can compromise the security of applications using this package. This code may allow unauthorized access to sensitive data, execute arbitrary commands, or manipulate system resources. The presence of such code can lead to severe ramifications, including data breaches, system instability, and loss of user trust.

How To Fix

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

npm uninstall desktopx

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, consider removing the desktopx package from your project until a secure version is released. You can do this by executing the command: 'npm uninstall desktopx'. Additionally, monitor your application for any unusual behavior that may indicate exploitation of this vulnerability.

Conclusion

The discovery of malicious code in the desktopx package highlights the importance of maintaining vigilance in software dependencies. Users are encouraged to update their packages promptly and utilize tools like Vulert to monitor for vulnerabilities in real-time.

See every vulnerability recorded for desktopx →

Share this vulnerability

FAQ

desktopx is an npm library used for creating and managing desktop applications with customizable features.

The malicious code can compromise application security, potentially allowing unauthorized access to sensitive data or system manipulation.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check your application without needing to sign up.

As a temporary measure, consider uninstalling the desktopx package and monitoring your application for any unusual behavior.

Detailed information about the vulnerability can be found in the GitHub repository of the malicious packages project.

How To Fix

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

npm uninstall desktopx

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