Critical Malicious Code Vulnerability in real-socket-rt Package

real-socket-rt Updated 02 Oct 2025

Summary

30/07/2025
CRITICAL
No i
Critical
Not published

MAL-2025-6372: Malicious code in real-socket-rt (npm). Affects real-socket-rt versions 2.12.1. 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

The real-socket-rt package is an npm library designed for real-time socket communication, enabling developers to build applications that require instant data exchange. However, this package has been identified to contain malicious code that compromises the security of any system it is installed on, posing significant risks to users and their data.

Vulnerability Detail

The vulnerability stems from embedded malicious code within the real-socket-rt package, which can lead to full system compromise. This malicious code can access sensitive information, including secrets and keys stored on the affected computer. The origin of this vulnerability is linked to the package's malicious intent, as indicated by its classification under CWE-506, which highlights the presence of harmful code. Users should be aware that simply removing the package may not eliminate all traces of the malicious software, as it may have already granted external entities control over the system.

How To Fix

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

npm uninstall real-socket-rt

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

Currently, there are no effective workarounds to mitigate the risks associated with the real-socket-rt package. The only recommended action is to uninstall the package and secure the system.

Conclusion

The real-socket-rt package contains critical malicious code that poses a severe threat to system security. 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 and ensure their applications remain secure.

See every vulnerability recorded for real-socket-rt →

Share this vulnerability

FAQ

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

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.

The consequences include unauthorized access to sensitive data, potential data breaches, and complete system compromise.

While removing the package is essential, there is no guarantee that all malicious software will be eliminated. It is advisable to perform a thorough security audit and restore the system from a clean backup.

Yes, but you should ensure that your application does not rely on the real-socket-rt package for its functionality, or find a secure alternative.

How To Fix

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

npm uninstall real-socket-rt

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