1-minute read of a 4 min report

GSocket keeps attackers connected after Linux web server fixes

By

1-minute read

What a defender needs to know

Attackers kept GSocket access to compromised Linux web servers after the web application flaws they used for entry were repaired, according to Microsoft Security Research. The client runs separately from the application: both the host and the operator connect outbound to a shared relay using a secret, so inbound firewall rules and blocks on operator-owned servers miss this connection path. Microsoft measured a 356.2% rise in devices with GSocket-related detections from March to August 2026 in its Defender for Endpoint telemetry; web applications and hosting accounted for 87.1% of attributable incidents in the analyzed data.

Prioritize exposed PHP, cPanel and Apache hosts. Correlate DeviceProcessEvents for gs-netcat, gsocket and web-service parent processes with files under /dev/shm/.gs-0, /tmp/.gsn_ora or /usr/bin/systemd-remount-d. Inspect cron jobs, systemd units and shell startup files for persistence, then check outbound network events for relay activity. The distribution hosts gsocket.io and gsgg.b-cdn.net are shared tooling infrastructure; investigate a match in host context.

Contain suspicious outbound access, patch the web application and remove the client and its launch hooks. After service restart or reboot, verify that the process and hooks remain absent and associated outbound relay traffic has stopped. A missing installer file is a blind spot because staging files can be deleted while the client persists.

Primary sources