CyberKit

Threat intel / Techniques and trends

GSocket keeps attackers on compromised Linux servers after patching

Attackers install the open-source GSocket relay tool on Linux web servers they have compromised, so access survives after the original web flaw is patched.

High severity. Active. Moderate confidence. First reported 11 Nov 2026, last activity 11 Nov 2026. Briefing updated 17 Nov 2026.

AI-written summaries of public reporting, each checked against at least two sources from different publishers. Check the sources before you act. Last refreshed 2026-11-18 14:09 UTC. How this is made.

What is not settled: Facts come from Microsoft's November 11 post, read through a summarizing fetch. BleepingComputer was seen only as a search excerpt, so it corroborates the campaign and nothing more. Microsoft names no actor and gives no absolute victim counts. CVE-2026-43284 is described as attempted in a few incidents, and Microsoft does not say whether any attempt succeeded. CISA's KEV catalog could not be checked from this environment, so no kev value is recorded.

In plain words

What happened

After breaking into a web server, attackers install GSocket, a free remote-access tool. It lets them back in through a shared relay, even after the website flaw they used is fixed.

Who is behind it

Microsoft does not name any group. It describes several unrelated threat actors using the same tool.

What they want

Microsoft does not state a goal. The tool gives the attacker a way back in that does not depend on their own servers.

What they did

Microsoft says the attackers first exploited a public web application for code execution, then used curl to download and run a script that installed GSocket. The tool was set to survive restarts and hide itself.

Who is at risk

Owners of internet-facing Linux servers, especially shared PHP and cPanel hosting, and the sites those servers run.

What to do

  • Treat a patched website as not yet clean. Look for GSocket on any server that was exploited, and remove it along with its persistence.
  • Block outbound connections to GSocket relay infrastructure, and use deny-by-default egress where you can.
  • Patch web applications, CMS plugins and the Linux kernel on internet-facing servers.
The technical version, for hunting and patching

What happened

GSocket (gs-netcat) relays traffic through a public relay network. Both the compromised host and the operator connect outward, so the host needs no inbound listener or public IP. Endpoints are identified by a shared secret rather than an IP address or hostname.

Who is behind it

No actor is named. Microsoft tracks the use across several groups and does not attribute it to one.

What they want

Microsoft does not state a goal. The design keeps persistent access without actor-owned command-and-control infrastructure.

What they did

Microsoft reports attacker deployment scripts that disguise the process, stage files in memory-backed directories, and install layered persistence through cron, systemd services, shell startup files and watchdog processes. It names these ATT&CK techniques: T1190, T1059.004, T1053.003, T1543.002, T1036, T1564.001, T1222.002, T1070.004, T1070.006, T1105 and T1090.002. Microsoft also reports that some intrusions tried CVE-2026-43284 to reach root from the web-service account. Devices with GSocket-related detections rose 356.2% from March to August 2026, not in a steady line.

Who is at risk

Shared hosting and cPanel servers running PHP or Apache are the main exposure in Microsoft's data, which attributes 87.1% of incidents to web applications and hosting. Education and research had the largest share of affected organizations at 30.7%, and technology and telecommunications followed at 22.9%. Microsoft says this likely reflects exposure, not deliberate targeting.

What to do

  • Hunt for gs-netcat or gsocket in process names and command lines, and for files under /dev/shm.
  • Audit cron, systemd units and shell startup files on exploited servers, since persistence is layered and often redundant.
  • Enable non-executable temporary directories where feasible, and alert on execution from hidden or world-writable paths.
  • Prioritize local privilege-escalation patches, including CVE-2026-43284, on internet-facing servers.

Vulnerabilities

CVEs in this briefing
CVEProductCVSSCISA KEVFixed in
CVE-2026-43284Linux kernel (Dirty Frag local privilege escalation)Not checked

ATT&CK techniques

Sectors: Cloud and hosting, Education, Technology. Regions: Global.

Open next

Sources

Newer: Fake Microsoft 365 outage notices push users to a "Restore Messages" link. Older: Cisco BroadWorks XML flaw (CVE-2026-20320) now exploited in the wild.