Critical Malicious Code Vulnerability in dgxeon-soket2 Package

dgxeon-soket2 Updated 28 Feb 2026

Summary

27/02/2026
CRITICAL
No i
Critical
Not published

MAL-2026-1075: Malicious code in dgxeon-soket2 (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 dgxeon-soket2 package is an npm library designed for socket communication in JavaScript applications. It is intended to facilitate real-time data exchange between clients and servers. However, this package has been identified as containing malicious code that compromises the security of any system it is installed on, making it a significant risk for developers and organizations using it.

Vulnerability Detail

The vulnerability originates from the presence of embedded malicious code within the dgxeon-soket2 package. This code can fully compromise any computer that has the package installed, allowing unauthorized access to sensitive information such as secrets and keys. The malicious nature of this code poses severe risks, as it may lead to data breaches, unauthorized control over systems, and potential exploitation of other connected resources.

How To Fix

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

npm uninstall dgxeon-soket2

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 you need similar functionality, consider using alternative packages that provide socket communication without known vulnerabilities. Always ensure to review the security status of any package before installation.

Conclusion

The dgxeon-soket2 package contains malicious code that poses a serious security threat to any system it is installed on. Immediate action is required to uninstall the package and secure any sensitive information. Utilizing tools like Vulert can help monitor and prevent future vulnerabilities.

See every vulnerability recorded for dgxeon-soket2 →

Share this vulnerability

FAQ

Immediately uninstall the dgxeon-soket2 package using 'npm uninstall dgxeon-soket2' and rotate any sensitive information stored on the affected system.

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

Keeping dgxeon-soket2 installed poses significant risks, including unauthorized access to sensitive data and potential control over your system by malicious actors.

Yes, consider using other well-reviewed socket communication libraries that do not have known vulnerabilities. Always check for security advisories before using any package.

Regularly audit your dependencies, use tools like Vulert for monitoring vulnerabilities, and stay informed about security advisories related to the packages you use.

How To Fix

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

npm uninstall dgxeon-soket2

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