Malicious Package in soket.io

soket.io Updated 02 Oct 2025

Summary

01/09/2020
CRITICAL
No i
Critical
9.8

GHSA-wp2p-q35g-3rjj: Malicious Package in soket.io. 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

soket.io is an npm package used for socket communication in JavaScript applications. It provides a convenient way to establish real-time, bidirectional communication between clients and servers. However, all versions of soket.io have been found to contain a malicious package. This package is designed to exploit users who make typographical errors when installing modules. Once executed, the package connects to a Command and Control server to execute arbitrary commands.

Vulnerability Detail

The malicious package in soket.io poses a significant security risk. When users mistakenly install this package, it opens a backdoor for attackers to gain control over the compromised machine. The package establishes a connection with a Command and Control server, enabling the execution of arbitrary commands. This can lead to unauthorized access, data breaches, and potential damage to the affected system. The vulnerability has a CVSS score of 9.8, indicating its critical severity.

How To Fix

No fixed version is published for this vulnerability.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Workaround

There is no specific workaround for this vulnerability. It is essential to follow the recommended steps for remediation to ensure the complete removal of the malicious package and mitigate any potential risks.

Conclusion

The presence of a malicious package in soket.io poses a critical security risk. If you discover this package in your environment, it is essential to follow the recommended steps for remediation. Revoke and rotate credentials, erase and reinstall the affected machine, and maintain a vigilant approach to software security. For further support and assistance in vulnerability remediation, you can reach out to DevNack.com.

See every vulnerability recorded for soket.io →

Share this vulnerability

FAQ

The malicious package takes advantage of users making typographical errors when installing modules. It masquerades as a legitimate package and, when executed, establishes a connection with a Command and Control server to execute arbitrary commands.

The consequences of this vulnerability can be severe. Attackers can gain unauthorized access to the compromised machine, leading to data breaches, unauthorized control, and potential damage to the system.

You can use Vulert's playground (https://vulert.com/scanner) to check if your application is affected by this vulnerability. Vulert monitors and alerts in real-time for open-source vulnerabilities using package-lock.json.

Yes, the recommended fix is to revoke and rotate all credentials found on the compromised machine, completely erase the affected machine, and reinstall the operating system. Additionally, ensure that all software and packages are obtained from trusted sources and regularly update and patch your system.

To prevent similar vulnerabilities, it is crucial to exercise caution when installing packages and ensure their authenticity. Double-check package names, verify the source, and rely on trusted package managers. Regularly update and patch your system to protect against known vulnerabilities.

Related vulnerabilities

Recent vulnerabilities recorded for soket.io.

How To Fix

No fixed version is published for this vulnerability.

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