Which versions of real-socket-rt are malicious?

The following npm versions of real-socket-rt are flagged malicious: 2.12.1. Treat any of these as compromised.

How do I remediate real-socket-rt if I installed it?

Remove real-socket-rt from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

I already installed real-socket-rt — how do I know if it already compromised me?

If real-socket-rt was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.

Is real-socket-rt part of a known attack campaign?

Yes — real-socket-rt is associated with the GHSA-3vr5-46x9-5526, RLMA-2025-04663, RLUA-2025-05932 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find real-socket-rt across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for real-socket-rt (version 2.12.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging real-socket-rt across your stack and pipelines.

Malicious package

real-socket-rtnpm

real-socket-rt is a confirmed malicious npm package (MAL-2025-6372) that executes malicious code on install (malicious version 2.12.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in real-socket-rt (npm)

MAL-2025-6372

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall real-socket-rt

What this malware does

Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

Malicious versions

1 flagged

2.12.1

Indicators of compromise (SHA-256)

897bfab5a2a7a305ab43ec0ffd356a56000463ad0f0c9c77731d1aa197aca121

b4f135acb0cf8e75c1b9789ab5335906fd2562293ee717e130736d238e5ce76e

638079d793ec9ffa7a2116f49ff82b6e35637769187b29c9fd88953e1afbae69

08d9aa1fef343c0a423bf118a2fec1585e421580432bc48ac94b97705393b88d

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for real-socket-rt (version 2.12.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging real-socket-rt across your stack and pipelines.
If you installed it — respond
Remove real-socket-rt from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If real-socket-rt was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks real-socket-rt before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.

Frequently asked questions

No. real-socket-rt on npm has been identified as a malicious package (version 2.12.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-3vr5-46x9-5526RLMA-2025-04663RLUA-2025-05932

References

Credits

ReversingLabs · finder

Detect & block this

O3 blocks real-socket-rt-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database