Critical Malicious Code Vulnerability in dgxeon-soket Package

dgxeon-soket Updated 28 Feb 2026

Summary

27/02/2026
CRITICAL
No i
Critical
Not published

MAL-2026-1074: Malicious code in dgxeon-soket (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-soket package is an npm library designed for socket communication in JavaScript applications. It facilitates real-time data exchange between clients and servers, making it a popular choice for developers building networked applications. However, this package has been compromised, leading to severe security risks for any system that has it installed.

Vulnerability Detail

The dgxeon-soket package contains embedded malicious code that can fully compromise any computer running it. This vulnerability originates from a malicious actor who has inserted harmful code into the package, potentially allowing unauthorized access to sensitive data, including secrets and keys stored on the affected system. The ramifications of this vulnerability are severe, as it can lead to data breaches and loss of control over the affected systems.

How To Fix

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

npm uninstall dgxeon-soket

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 and securing your system. It is recommended to monitor your environment for any signs of compromise and take necessary actions to secure your data.

Conclusion

The dgxeon-soket package has been identified as containing malicious code that can compromise systems. Immediate action is required to uninstall the package and secure any sensitive information. Utilizing tools like Vulert can help in monitoring for such vulnerabilities in the future.

See every vulnerability recorded for dgxeon-soket →

Share this vulnerability

FAQ

Immediately uninstall the dgxeon-soket package using the command npm uninstall dgxeon-soket 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 any signup.

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

No, there is currently no patched version of dgxeon-soket available. The only course of action is to uninstall the package.

Regularly monitor your dependencies for vulnerabilities using tools like Vulert, and ensure to keep your packages updated to their latest versions.

How To Fix

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

npm uninstall dgxeon-soket

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