Critical Malicious Code Vulnerability in sokettry Package

sokettry Updated 28 Feb 2026

Summary

27/02/2026
CRITICAL
No i
Critical
Not published

MAL-2026-1079: Malicious code in sokettry (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 Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The sokettry package is an npm library designed for socket communication, enabling developers to create real-time applications with ease. It is widely used in various projects due to its simplicity and effectiveness. 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 sokettry package. This code can compromise any computer that has the package installed, allowing unauthorized access to sensitive information, including secrets and keys. The ramifications of this vulnerability are severe, as it can lead to full control of the affected system by an external entity. Users are advised to treat any system with this package as fully compromised.

How To Fix

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

npm uninstall sokettry

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 sokettry package entirely. Users should ensure that they do not run any applications that depend on this package until it has been removed.

Conclusion

The sokettry package poses a critical security risk due to the presence of malicious code. Immediate action is required to uninstall the package and secure any compromised systems. Users are encouraged to monitor their applications for vulnerabilities using tools like Vulert, which can alert them to potential threats in real-time.

See every vulnerability recorded for sokettry →

Share this vulnerability

FAQ

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

You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.

No, there is currently no patched version of the sokettry package available. The only solution is to uninstall it.

Failure to remove sokettry can result in unauthorized access to your system, potentially leading to data breaches and loss of sensitive information.

It is highly discouraged to continue using any application that relies on sokettry until the package is removed and a secure alternative is found.

How To Fix

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

npm uninstall sokettry

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