Critical Security Breach in dgxeon-soket3: Malicious Code Detected

dgxeon-soket3 Updated 28 Feb 2026

Summary

27/02/2026
CRITICAL
No i
Critical
Not published

MAL-2026-1076: Malicious code in dgxeon-soket3 (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

dgxeon-soket3 is an npm package designed for socket communication in JavaScript applications. It is commonly used for real-time data exchange between clients and servers. However, it has been identified as containing malicious code that compromises the security of any system where it is installed. This vulnerability poses a significant risk to sensitive data and system integrity.

Vulnerability Detail

The dgxeon-soket3 package has been flagged for containing embedded malicious code. This vulnerability originates from the package's source code, which has been compromised, allowing unauthorized access to systems that utilize it. The ramifications of this vulnerability are severe, as any computer running this package is considered fully compromised. Attackers may gain access to sensitive information, including secrets and keys, stored on the affected systems. The malicious code can persist even after the package is removed, making it critical for users to take immediate action.

How To Fix

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

npm uninstall dgxeon-soket3

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. The best course of action is to uninstall the dgxeon-soket3 package and ensure that all sensitive information is secured.

Conclusion

The dgxeon-soket3 package has been identified as containing malicious code that poses a significant security risk. Immediate action is required to remove the package and secure any sensitive information. Users are encouraged to utilize tools like Vulert to monitor for vulnerabilities in their applications.

See every vulnerability recorded for dgxeon-soket3 →

Share this vulnerability

FAQ

Immediately uninstall the dgxeon-soket3 package and rotate any sensitive information stored on the affected system.

You can use Vulert to monitor and alert for open-source vulnerabilities in your software. Visit Vulert Scanner to check if your application is affected without any signup.

Failure to address this vulnerability can lead to unauthorized access to sensitive data, system compromise, and potential data breaches.

If your system has been compromised, it is crucial to rotate all secrets and keys and assess the extent of the breach. Consider restoring from a backup if available.

While removing the dgxeon-soket3 package is essential, there is no guarantee that all malicious software will be removed. A thorough security audit is recommended.

How To Fix

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

npm uninstall dgxeon-soket3

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