Critical Malicious Code Vulnerability in socket-dgxeon Package

socket-dgxeon Updated 28 Feb 2026

Summary

27/02/2026
CRITICAL
No i
Critical
Not published

MAL-2026-1078: Malicious code in socket-dgxeon (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 Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

The socket-dgxeon package is an npm library designed for socket communication in JavaScript applications. It is intended to facilitate data transmission over networks. However, this package has been identified as containing malicious code, posing significant security risks to any system that has it installed.

Vulnerability Detail

The vulnerability originates from the inclusion of malicious code within the socket-dgxeon package. This code can compromise the entire system, allowing unauthorized access to sensitive information such as secrets and keys. The presence of this malicious code means that any computer running this package should be considered fully compromised, and there is no guarantee that simply removing the package will eliminate all traces of the malicious software.

How To Fix

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

npm uninstall socket-dgxeon

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

There are no effective workarounds for this vulnerability other than removing the package entirely. Ensure that you monitor your system for any signs of compromise after removal.

Conclusion

The socket-dgxeon package contains malicious code that compromises the security of any system using it. Immediate removal of the package and rotation of sensitive information is necessary to mitigate risks. Users should remain vigilant for any signs of compromise even after removal.

See every vulnerability recorded for socket-dgxeon →

Share this vulnerability

FAQ

You should uninstall the socket-dgxeon package immediately and rotate any sensitive information stored on the affected system.

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.

Keeping socket-dgxeon installed poses a significant risk as it can lead to unauthorized access to your system and sensitive data.

No, there is currently no patched version available for socket-dgxeon. The only action is to remove the package.

While removing the package is essential, it does not guarantee that your system is entirely safe. You should monitor for any signs of compromise.

How To Fix

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

npm uninstall socket-dgxeon

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