malware
Published 2026-11-12
Verified 2026-11-13

Microsoft says threat actors are planting the open-source GSocket relay tool on compromised Linux web servers to keep access after the exploited flaw is patched

Microsoft published research on its Security Blog on 11 November 2026 (19:49 UTC = 03:49 AWST 12 Nov) on threat actors using GSocket, a legitimate open-source tool, for command and control on compromised Linux servers.

Microsoft says that after exploiting internet-facing web applications, threat actors used curl to download and run a script that stages a GSocket client in writable or memory-backed paths such as /dev/shm; the compromised host and the operator both connect outbound to the public Global Socket Relay Network, so the host needs no inbound listener and there is no actor-owned IP address or domain to block, although egress filtering and outbound monitoring can see the traffic.

Microsoft says the actors disguised GSocket with kernel-thread-like process names and persisted through cron, systemd, shell profiles, watchdogs and redundant copies, and that in a few incidents they tried to exploit the Linux kernel flaw CVE-2026-43284 (Dirty Frag) to gain root.

Because GSocket runs independently of the exploited application, Microsoft says patching the vulnerability does not remove the relay client or its persistence. Per Microsoft Defender for Endpoint telemetry, devices with GSocket-related detections rose 356.2% from March through August 2026; web applications and hosting made up 87.1% of attributable incidents, with PHP web applications and cPanel hosting at 63.9% and Apache at 24.3% within that group; education and research was the largest share of affected organisations (30.7%). (source: Microsoft Security Blog)

Product
Linux web servers (PHP web applications, cPanel hosting, Apache) abused with the GSocket relay tool
Versions
n/a — post-exploitation tooling, not a GSocket vulnerability; Microsoft names CVE-2026-43284 (Dirty Frag) as one privilege-escalation attempt
Exploited in Australia?
unknown
Patch to
Remediate the host as well as the flaw: remove the GSocket client, its persistence (cron, systemd, shell profiles) and staged files, then verify outbound connections to the relay have stopped; apply deny-by-default egress rules and monitor connections to relay infrastructure; keep internet-facing web apps, CMS platforms and plugins current (Microsoft advice).

tech network