Malicious Code Vulnerability in Ultimate-Websocket Package

ultimate-websocket Updated 05 Oct 2026

Summary

04/10/2026
CRITICAL
No i
Critical
Not published

MAL-2026-17529: Malicious code in ultimate-websocket (npm). Affects ultimate-websocket versions 1.0.0. 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 MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

Ultimate-websocket is an npm package designed for real-time communication in web applications. It allows developers to implement WebSocket protocols easily, facilitating efficient data transfer between clients and servers. However, this package has been found to contain a serious vulnerability that exposes users to potential malicious code execution.

Vulnerability Detail

The vulnerability originates from the package's dependency on 'node-net-pool', which is fetched from a mutable GitHub tarball URL. This bypasses the npm registry, allowing the installation of arbitrary code without integrity checks. The lack of version pinning or commit SHA means that any changes made to the tarball can introduce malicious code, which is executed during the installation process. This poses a significant risk as it allows attackers to run arbitrary code on the installer's machine, potentially leading to data breaches or system compromise.

How To Fix

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

npm uninstall ultimate-websocket

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 temporary workaround, avoid using the ultimate-websocket package until a secure version is released. If you must use it, consider manually reviewing the dependency and its source to ensure no malicious code is present.

Conclusion

The ultimate-websocket package contains a critical vulnerability that allows for the execution of malicious code during installation. Users are advised to update to the latest version or avoid using the package until a fix is implemented. Regular monitoring of dependencies is crucial to maintain application security.

See every vulnerability recorded for ultimate-websocket →

Share this vulnerability

FAQ

The vulnerability allows for the execution of arbitrary code during installation due to a dependency fetched from an untrusted source.

You can use Vulert's playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.

The risks include potential data breaches, unauthorized access to system resources, and execution of malicious actions on the user's machine.

Yes, temporarily avoid using the package or review its dependencies manually to ensure they are secure.

How To Fix

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

npm uninstall ultimate-websocket

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