Malicious Code Detected in dshelx Package - Security Alert

dshelx Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-18939: Malicious code in dshelx (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 dshelx package is a Node.js library designed for specific functionalities within the npm ecosystem. It is utilized by developers for various applications, providing essential features that enhance software development. However, this package has been identified to contain malicious code, posing a significant risk to users and their applications.

Vulnerability Detail

The vulnerability in the dshelx package originates from the inclusion of malicious code that can compromise the security of applications using this package. This malicious code can lead to unauthorized access, data breaches, or other harmful actions within the affected software environment. The severity of this vulnerability necessitates immediate attention from developers and users to mitigate potential risks.

How To Fix

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

npm uninstall dshelx

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 remove the dshelx package from your project until a secure version is available. Use the following command to uninstall it: 'npm uninstall dshelx'. This will help prevent any potential exploitation of the vulnerability while you await a fix.

Conclusion

The dshelx package has been identified to contain malicious code, posing a significant security risk to applications utilizing it. Immediate action is required to update or remove the package to protect against potential exploitation. Utilizing tools like Vulert can help monitor and manage vulnerabilities effectively.

See every vulnerability recorded for dshelx →

Share this vulnerability

FAQ

The dshelx package is a Node.js library used in various applications within the npm ecosystem, providing specific functionalities for developers.

The malicious code found in the dshelx package can lead to unauthorized access and potential data breaches, posing significant security risks.

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.

If an immediate update is not possible, consider uninstalling the dshelx package as a temporary workaround to mitigate risks until a secure version is available.

Detailed information about the dshelx vulnerability can be found on the GitHub repository of the malicious packages project at https://github.com/ossf/malicious-packages.

How To Fix

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

npm uninstall dshelx

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