Malicious Code Vulnerability in turbo-ws Package
Summary
MAL-2026-16440: Malicious code in turbo-ws (npm). Affects turbo-ws versions 1.0.0. No fix is published. How to fix ↓
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.
No signup required · Results in about 60 seconds
Background
The turbo-ws package is an npm library designed for WebSocket communication, providing a lightweight and efficient way to handle real-time data transfer in web applications. However, it has been found to contain a serious vulnerability that allows for the execution of malicious code during installation, posing significant risks to users and their systems.
Vulnerability Detail
The vulnerability originates from the package's dependency declaration in its package.json file, which points to an HTTPS tarball of an unrelated GitHub repository. This means that when users install turbo-ws, they inadvertently fetch and execute code from an external source that is not verified or controlled by the package maintainers. The lack of integrity checks and the execution of lifecycle scripts can lead to arbitrary code execution on the user's machine, allowing attackers to potentially compromise systems and data.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall turbo-wsIf 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, users can avoid installing the turbo-ws package until a secure version is released. Alternatively, consider using a different package for WebSocket communication that does not have known vulnerabilities.
Conclusion
The turbo-ws package has a critical vulnerability that allows for the execution of malicious code during installation. Users should take immediate action to update or remove the package and consider using alternative solutions until a secure version is available. Regular monitoring for vulnerabilities using tools like Vulert is highly recommended.
See every vulnerability recorded for turbo-ws →
FAQ
The vulnerability involves the execution of malicious code from an external source during the installation of the package.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check your application without needing to sign up.
If you have installed turbo-ws, it is recommended to uninstall it immediately and check for any signs of compromise on your system.
Users should check the npm registry for the latest version of turbo-ws to see if a patch has been released.
Using vulnerable packages can lead to unauthorized access, data breaches, and potential control over your system by malicious actors.
