HighCVE-2026-43284 5 Hunt LeadsIOCsHands-On-KeyboardGSocketMicrosoft Threat Intelligence

Patched the Web App? GSocket Keeps Attackers on Your Linux Server

Microsoft says multiple groups plant GSocket on hacked Linux web servers to keep access after the entry bug is patched, using a public relay network that leaves no attacker IP or domain to block.

Patching the hole attackers came in through doesn’t mean they’ve left. Microsoft Threat Intelligence reports that several unrelated groups are planting GSocket, an open-source remote access tool, on hacked Linux web servers so they keep a way back in after the original vulnerability is fixed. Microsoft says devices with GSocket-related detections rose 356.2% from March to August 2026, mostly PHP sites, cPanel hosting and Apache servers, with universities and research groups the most affected.

For defenders

Way in: attackers exploit an internet-facing web app (T1190 (Exploit Public-Facing Application)), then the web server process runs curl to fetch a script from GSocket’s own site and pipes it to bash (T1059.004 (Command and Scripting Interpreter: Unix Shell), T1105 (Ingress Tool Transfer)). The script profiles the host, picks the right binary and stages it in hidden or memory-backed paths such as /dev/shm/.gs-0/ (T1564.001 (Hide Artifacts: Hidden Files and Directories)).

Staying in: the client runs as systemd-remount-d, or as /usr/bin/defunct launched with exec -a to show the kernel-thread-style name [kaluad] (T1036 (Masquerading)). Persistence is layered: cron, a defunct.service systemd unit, shell profiles, watchdogs and spare copies (T1053.003 (Scheduled Task/Job: Cron), T1543.002 (Create or Modify System Process: Systemd Service), T1546.004 (Event Triggered Execution: Unix Shell Configuration Modification)). Attackers then backdate file timestamps and delete staging files (T1070.006 (Indicator Removal: Timestomp), T1070.004 (Indicator Removal: File Deletion)). In a few cases they tried Linux kernel bug CVE-2026-43284 (“Dirty Frag”) to get root (T1068 (Exploitation for Privilege Escalation)).

Why blocking IPs fails: the server and the operator both connect outbound to the public Global Socket Relay Network, which pairs them by a shared secret over an encrypted session (T1090.002 (Proxy: External Proxy)). There’s no attacker-owned IP or domain to block, no inbound listener, and the secret can be sent to the operator over Telegram, Discord or a webhook. The download hosts (gsocket[.]io, cdn[.]gsocket[.]io, gsgg[.]b-cdn[.]net) belong to the tool, not the attackers: alert on them from servers rather than treating them as attacker infrastructure. Microsoft published five Defender hunting queries, reproduced in the Hunt Lead report below.

Files
/dev/shm/.gs-0/gs-netcat_mini-linux-x86_64 (SHA256 d94f75a70b5cabaf786ac57177ed841732e62bdcc9a29e06e5b41d9be567bcfa)
/dev/shm/.gs-0/gs-netcat_mini-linux-aarch64 (SHA256 f95c4d029e6784e3849b4d1e2e2ae1a661187236ef7c5d487c71158a290a03b5)
/tmp/systemd-remount-d, /usr/bin/systemd-remount-d (SHA256 55d141bb2f62c527c3fea3413b8429fed7d52633d0b123b5e611bfa42165229f)
/tmp/.gsn_ora (SHA256 12450bafc7a4398040e1ad3a16dbf4dbc79b6a8f83ef306c4f0f73f59886f06c)
/usr/bin/defunct · defunct.service · process name [kaluad]

What it means for you

If you run a website on a Linux server or shared hosting, a fixed plugin or patched app doesn’t prove the attacker is gone. They may have left a quiet back door that phones out through a public relay and looks like a normal system process. Home users with no server have nothing to do.

Do this now

  1. After any web app compromise, check the server itself: cron jobs, systemd services, shell startup files and /dev/shm, not just the app.
  2. Patch the Linux kernel on internet-facing servers, including CVE-2026-43284.
  3. Mount /tmp and /dev/shm noexec where you can, and block web servers from making outbound connections they don’t need.
  4. If you find GSocket you didn’t install, rebuild the server; deleting one copy won’t remove the others.

Source article: The global socket: how threat actors are weaponizing GSocket for stealthy C2
Publisher: Microsoft Threat Intelligence (Yash Gund, Sumith Maniath, Microsoft Security Research)
Published: Nov. 11, 2026
URL: https://www.microsoft.com/en-us/security/blog/2026/11/11/global-socket-how-threat-actors-weaponizing-gsocket-stealthy-c2/

Executive Summary

Microsoft Threat Intelligence reports that multiple unrelated threat actors, none named or tracked as a single group, are deploying GSocket, an open-source relay-based remote access tool published by The Hacker’s Choice, on compromised Linux servers to keep access after the vulnerability used for initial entry has been patched. Defender for Endpoint telemetry shows devices with GSocket-related detections rising 356.2% from March to August 2026; web applications and hosting made up 87.1% of attributable incidents, with PHP applications and cPanel hosting at 63.9% and Apache at 24.3%, and education and research (30.7%) and technology and telecommunications (22.9%) the most affected sectors, which Microsoft attributes to exposure rather than deliberate targeting. The observed chain starts with exploitation of an internet-facing web application, after which the web-service process uses curl to download a remote installer script from GSocket’s distribution hosts and runs it with bash; the script profiles the host, selects a client for the architecture, stages it in writable or memory-backed paths such as /dev/shm/.gs-0, and connects outbound to the Global Socket Relay Network. The actors then disguise the client with system-service or kernel-thread-like names (systemd-remount-d, [kaluad] via exec -a), layer persistence through cron, systemd (defunct.service), shell profiles, watchdogs and redundant copies, change permissions, backdate timestamps and delete staging files, and in a few incidents attempt Linux kernel privilege escalation through CVE-2026-43284 (Dirty Frag). Because the compromised host and the operator both connect outbound to a shared public relay and are matched by a secret that can be exfiltrated over Telegram, Discord or a webhook, there is no actor-owned IP address or domain to block, and patching the original flaw leaves the access in place. The objective is durable, low-maintenance access to web servers. Hunt leads, false positive expectations, Microsoft’s published hunting queries and indicators are detailed below.

ATT&CK chain: Initial Access → Execution → Persistence → Privilege Escalation → Defense Evasion → Command and Control

Hunt Lead Grid

Hunt Lead Level Hunt Lead Name ATT&CK Risk of False Positives
1 (Junior) GSocket Staging and Persistence Artifacts T1564.001 (Hide Artifacts: Hidden Files and Directories), T1543.002 (Create or Modify System Process: Systemd Service) Low. Paths like /dev/shm/.gs-*, /tmp/.gsn_ora and the names systemd-remount-d, defunct and defunct.service do not exist on a stock Linux server; the lead anchors on those exact names and the four published SHA256s.
1 (Junior) GSocket Installer Downloads from Servers T1105 (Ingress Tool Transfer) Low on servers, Medium elsewhere. Administrators and researchers do use GSocket legitimately; the lead anchors on servers, especially web servers, contacting the tool’s distribution hosts, which almost never has a business reason.
2 (Pro) GSocket Processes, Including Renamed and Kernel-Thread Masquerades T1036 (Masquerading) Medium. Real kernel threads show bracketed names but have no executable path; the lead anchors on user-space processes with a bracketed name or a service-like name that runs from /tmp, /dev/shm or an unpackaged /usr/bin file.
2 (Pro) Web Server Process Running curl Piped to bash T1059.004 (Command and Scripting Interpreter: Unix Shell), T1190 (Exploit Public-Facing Application) Medium. Some PHP and Node applications shell out legitimately (image tools, mailers), but a web server or language runtime spawning a shell that downloads and executes a remote script is rare; the lead anchors on that lineage plus the download-and-execute pattern.
3 (Elite) Layered Persistence and Timestomping by the Web-Service Account T1053.003 (Scheduled Task/Job: Cron), T1546.004 (Event Triggered Execution: Unix Shell Configuration Modification), T1070.006 (Indicator Removal: Timestomp), T1090.002 (Proxy: External Proxy) Medium. Configuration management and control panels write cron and service files routinely; the lead anchors on several persistence surfaces changing within minutes from one process tree descended from a web service, combined with timestamp copying and a new long-lived outbound session.

GSocket Staging and Persistence Artifacts

In the analyzed intrusions, curl downloaded gs-netcat_mini-linux-x86_64 or gs-netcat_mini-linux-aarch64 into the dot-prefixed directory /dev/shm/.gs-0, and a GsNetcat-detected file was also found at /tmp/.gsn_ora. One build ran from /tmp/systemd-remount-d and /usr/bin/systemd-remount-d; in another context the payload was copied to /usr/bin/defunct, given chmod 700, backed by a defunct.service systemd unit with a multi-user.target.wants link, and then the staged gs-netcat file and the /dev/shm/.gs-0 directory were deleted. The detection logic is a file sweep and file-creation rule for any path beginning /dev/shm/.gs-, the names systemd-remount-d, .gsn_ora, defunct and defunct.service anywhere, and the four published SHA256s; Microsoft’s own queries for this are reproduced below and can be adapted to any EDR with file events. Because staging files are deleted after install, the persistent names under /usr/bin and the systemd unit directories are the more durable finds.

let badSHA256 = dynamic([
    "d94f75a70b5cabaf786ac57177ed841732e62bdcc9a29e06e5b41d9be567bcfa",
    "f95c4d029e6784e3849b4d1e2e2ae1a661187236ef7c5d487c71158a290a03b5",
    "55d141bb2f62c527c3fea3413b8429fed7d52633d0b123b5e611bfa42165229f",
    "12450bafc7a4398040e1ad3a16dbf4dbc79b6a8f83ef306c4f0f73f59886f06c"
]);
DeviceFileEvents
| where Timestamp > ago(7d)
| where SHA256 in~ (badSHA256)
| project Timestamp, DeviceName, ActionType, FileName, FolderPath, SHA256,
    InitiatingProcessFileName, InitiatingProcessCommandLine
| order by Timestamp desc
DeviceFileEvents
| where Timestamp > ago(7d)
| where FolderPath startswith "/dev/shm/.gs-"
    or FileName in~ ("systemd-remount-d", ".gsn_ora", "defunct", "defunct.service")
| project Timestamp, DeviceName, ActionType, FileName, FolderPath, SHA256,
    InitiatingProcessFileName, InitiatingProcessCommandLine
| order by Timestamp desc

Run the queries (published by Microsoft, Advanced Hunting KQL for Defender XDR) or their equivalents in your EDR, and run a one-off filesystem sweep (find over /dev/shm, /tmp, /usr/bin and /etc/systemd/system, plus rpm -Vf or debsums to flag unpackaged files in /usr/bin) across all Linux servers. Extend Microsoft’s seven-day window to at least 180 days, since the activity has grown since March 2026 and the point of GSocket is long-lived access. Scope to internet-facing web servers and shared hosting first. False positives should be near zero; an administrator who installed GSocket deliberately would use its default names, which the process lead covers. Hash blocking alone is the wrong control because GSocket is open source and trivially rebuilt, so the path and name anchors matter more than the hashes. Any hit means attacker persistence on the host: escalate, preserve the files, and run the persistence lead to find every copy before removal.

Hunt Lead Level: 1 (Junior Analyst)

ATT&CK: Defense Evasion → T1564.001 (Hide Artifacts: Hidden Files and Directories); Persistence → T1543.002 (Create or Modify System Process: Systemd Service) (mapping per source article)

Sources: “The global socket: how threat actors are weaponizing GSocket for stealthy C2”, Microsoft Threat Intelligence, Nov. 11, 2026, https://www.microsoft.com/en-us/security/blog/2026/11/11/global-socket-how-threat-actors-weaponizing-gsocket-stealthy-c2/ (source article; artifacts and queries)

GSocket Installer Downloads from Servers

After exploiting a web application, the actors ran curl against GSocket’s distribution endpoints to fetch the installer and client: hxxps://gsocket[.]io/y in download-and-execute commands, hxxps://gsocket[.]io/install.sh as an attempted target, and client binaries from hxxps://gsgg[.]b-cdn[.]net/bin/gs-netcat_mini-linux-x86_64 and hxxps://cdn[.]gsocket[.]io/bin/gs-netcat_mini-linux-aarch64. Microsoft stresses that these are tool distribution hosts, not actor-owned command and control, so they will appear in legitimate use too; what is unusual is a production server reaching them. The detection logic is a network and command-line rule for any server process contacting gsocket[.]io, cdn[.]gsocket[.]io or gsgg[.]b-cdn[.]net, or any process command line containing those hosts; Microsoft’s queries are reproduced below exactly as published.

DeviceProcessEvents
| where Timestamp > ago(7d)
| where ProcessCommandLine has "gsocket.io"
    or ProcessCommandLine has "gsgg.b-cdn.net"
| project Timestamp, DeviceName, AccountName, FileName,
    ProcessCommandLine, InitiatingProcessFileName
| order by Timestamp desc
DeviceNetworkEvents
| where Timestamp > ago(7d)
| where RemoteUrl has_any ("gsocket.io", "gsgg.b-cdn.net")
| project Timestamp, DeviceName, ActionType, RemoteUrl, RemoteIP, RemotePort,
    InitiatingProcessFileName, InitiatingProcessAccountName
| order by Timestamp desc

Use DNS resolver logs, proxy and egress firewall logs, and EDR network and process telemetry; on shared hosting without EDR, web server error logs and auditd execve records can show the curl command. Look back 180 days or as far as DNS logs allow. Scope to servers; on analyst and administrator workstations, legitimate GSocket use is possible and should be confirmed with the user rather than alerted at high severity. Blocking the parent domain b-cdn.net would break unrelated sites served by that CDN, so block or alert on the exact gsgg[.]b-cdn[.]net hostname, and consider blocking gsocket[.]io for server networks where nobody needs the tool. A server-side hit is a strong signal of post-exploitation and should be escalated together with the artifact lead for the same host.

Hunt Lead Level: 1 (Junior Analyst)

ATT&CK: Command and Control → T1105 (Ingress Tool Transfer) (mapping per source article)

Sources: Microsoft Threat Intelligence (above), source article

GSocket Processes, Including Renamed and Kernel-Thread Masquerades

Microsoft observed a GsNetcat binary executing as systemd-remount-d, a name that looks like a systemd helper, and in another intrusion bash used exec -a to launch /usr/bin/defunct with the argument-zero name [kaluad], mimicking a kernel worker thread in process listings. The actors chose names that blend into ps output on a busy server. The detection logic has two parts: Microsoft’s published process query for GSocket by name or command line, reproduced below, and a masquerade rule that flags any process whose name or argv[0] is bracketed like a kernel thread but which has a real executable path (kernel threads have none and their parent is kthreadd, PID 2), or whose name starts with systemd- but whose binary is not owned by an installed package or runs from /tmp or /dev/shm.

DeviceProcessEvents
| where Timestamp > ago(7d)
| where FileName has_any ("gs-netcat", "gsocket")
    or ProcessCommandLine has_any ("gsocket.io", "gs-netcat", "gsnetcat")
| project Timestamp, DeviceName, AccountName, FileName, FolderPath,
    ProcessCommandLine, InitiatingProcessFileName
| order by Timestamp desc

Use EDR process telemetry on Linux, auditd execve logging, or a scheduled script that compares /proc/<pid>/comm and cmdline against /proc/<pid>/exe and the parent PID. Baseline the bracketed and systemd-prefixed process names across a sample of hosts for 30 days, then run the rule continuously and sweep current process lists now. Scope to all Linux servers, prioritizing web and hosting servers. False positives come from unusual but legitimate daemons with odd names; resolve them by package ownership of the executable, never by name alone, since names are exactly what the attacker controls. Killing the process is the wrong first step because watchdogs and redundant copies respawn it; capture /proc/<pid>/exe and environment (which may hold the GSocket secret), then run the persistence lead. The masquerade rule generalizes well beyond GSocket to most Linux implants.

Hunt Lead Level: 2 (Pro)

ATT&CK: Defense Evasion → T1036 (Masquerading) (mapping per source article)

Sources: Microsoft Threat Intelligence (above), source article

Web Server Process Running curl Piped to bash

Every RCE-based intrusion Microsoft analyzed began with a vulnerable internet-facing application (PHP applications, Java and Node web apps among the alert types) executing an encoded command in the web-service context, which used curl to download the GSocket script and ran it with bash; the alerts that fired included suspicious shell execution from PHP applications, web server applications and scripting runtimes, and suspicious piped commands. The detection logic is a process-lineage rule: alert when a web server or application runtime (apache2, httpd, nginx, php-fpm, php, lsphp, java, node, python running a web framework) is an ancestor of sh or bash that runs curl or wget with output piped to a shell, or writes to /dev/shm or /tmp and then executes the written file, or decodes base64 and executes the result. Running as the web-service account (www-data, apache, nobody, or a cPanel user) raises confidence.

Use EDR process lineage on Linux or auditd execve rules scoped to the web-service UIDs; on cPanel servers, Imunify or similar host agents can supply the same lineage. Baseline 30 days of child processes for each web server to learn legitimate helpers (ImageMagick, sendmail, git for deploy hooks), then look back as far as telemetry allows and run continuously. Scope to every internet-facing web server, including forgotten departmental and research sites, which Microsoft identifies as the most exposed group. Allowlist legitimate helpers by full command line and path, not by binary name, because curl itself is legitimate. Blocking curl on web servers is a poor control that breaks applications and is bypassed with wget or PHP’s own HTTP functions; egress restriction for web-service accounts is the better fix. A hit indicates a working exploit on that application: escalate, identify the vulnerable app from the web logs at the same timestamp, and remember that patching it will not remove anything already installed.

Hunt Lead Level: 2 (Pro)

ATT&CK: Execution → T1059.004 (Command and Scripting Interpreter: Unix Shell); Initial Access → T1190 (Exploit Public-Facing Application) (mapping per source article)

Sources: Microsoft Threat Intelligence (above), source article

Layered Persistence and Timestomping by the Web-Service Account

Microsoft found that the actors did not rely on one persistence method: they created cron entries in the same window as the deployment script, a defunct.service systemd unit linked into multi-user.target.wants, shell-profile entries, watchdogs and redundant copies, then ran touch to give /usr/bin/defunct and defunct.service older timestamps and copied timestamps onto the service-like payload name so the files would not stand out by date. The client then connects outbound to the Global Socket Relay Network, a shared public relay, to be paired with the operator. The correlation to build groups, per host and within a short window (for example 15 minutes), changes to two or more persistence surfaces (crontabs and /etc/cron.*, systemd unit files and .wants links, ~/.bashrc, ~/.profile and /etc/profile.d) made by one process tree that descends from a web service or from a shell started by one; adds touch -r or touch -d invocations against the same files; and finishes with a new long-lived outbound TCP session from a process with a bracketed or service-like name. Microsoft’s alerts for suspicious cron job creation, suspicious Linux service creation and suspicious timestamp modification correspond to the individual parts.

Use EDR file and process telemetry, auditd watches on cron, systemd and profile paths (-w /etc/cron.d -p wa and similar), file integrity monitoring, and egress NetFlow or firewall logs to see sessions to relay infrastructure. Baseline 30 days of changes to these paths, which on a hosting server mostly come from the control panel and configuration management, and look back 180 days. Scope to web and hosting servers. Allowlist the control panel and configuration-management agents by signed path and parent, not by user, since the attacker may reach root through Dirty Frag. Removing only the systemd unit or only the cron line is the wrong response because the other layers restore access, and stopping the process alone does not remove persistence, as Microsoft notes. Patch CVE-2026-43284 on internet-facing servers to limit root escalation. A correlated hit should be treated as a confirmed backdoor: escalate, and prefer rebuilding the host from known-good images over in-place cleanup.

Hunt Lead Level: 3 (Elite)

ATT&CK: Execution, Persistence → T1053.003 (Scheduled Task/Job: Cron) (mapping per source article); Persistence → T1543.002 (Create or Modify System Process: Systemd Service) (mapping per source article); Persistence → T1546.004 (Event Triggered Execution: Unix Shell Configuration Modification) (our mapping; Microsoft describes shell-profile persistence but did not list a technique for it); Defense Evasion → T1070.006 (Indicator Removal: Timestomp) (mapping per source article); Command and Control → T1090.002 (Proxy: External Proxy) (mapping per source article)

Sources: Microsoft Threat Intelligence (above), source article

Hash Appendix

GSocket gs-netcat clients

All four SHA256s come from the source article. For the x86-64 build, the MD5 and SHA1 were sourced via OTX AlienVault; OTX had no MD5 or SHA1 for the other three files. GSocket is a public open-source tool, so these hashes identify specific builds, not every copy; rebuilt binaries will not match.

MD5s

d75cb9920d1d3d280518ddccfe4789d2  # gs-netcat_mini-linux-x86_64 -> /dev/shm/.gs-0/, GSocket client x86-64 (sourced via OTX)
(not available)  # gs-netcat_mini-linux-aarch64 -> /dev/shm/.gs-0/, GSocket client AArch64
(not available)  # systemd-remount-d -> /tmp/ and /usr/bin/, renamed GSocket client
(not available)  # .gsn_ora -> /tmp/.gsn_ora, hidden GSocket client

SHA1s

18821dbb53892d6faa14b1f063517a0302057290  # gs-netcat_mini-linux-x86_64 -> /dev/shm/.gs-0/, GSocket client x86-64 (sourced via OTX)
(not available)  # gs-netcat_mini-linux-aarch64 -> /dev/shm/.gs-0/, GSocket client AArch64
(not available)  # systemd-remount-d -> /tmp/ and /usr/bin/, renamed GSocket client
(not available)  # .gsn_ora -> /tmp/.gsn_ora, hidden GSocket client

SHA256s

d94f75a70b5cabaf786ac57177ed841732e62bdcc9a29e06e5b41d9be567bcfa  # gs-netcat_mini-linux-x86_64 -> /dev/shm/.gs-0/, GSocket client x86-64
f95c4d029e6784e3849b4d1e2e2ae1a661187236ef7c5d487c71158a290a03b5  # gs-netcat_mini-linux-aarch64 -> /dev/shm/.gs-0/, GSocket client AArch64
55d141bb2f62c527c3fea3413b8429fed7d52633d0b123b5e611bfa42165229f  # systemd-remount-d -> /tmp/ and /usr/bin/, renamed GSocket client
12450bafc7a4398040e1ad3a16dbf4dbc79b6a8f83ef306c4f0f73f59886f06c  # .gsn_ora -> /tmp/.gsn_ora, hidden GSocket client

References Appendix

  • “The global socket: how threat actors are weaponizing GSocket for stealthy C2”, Microsoft Threat Intelligence (Yash Gund, Sumith Maniath, Microsoft Security Research), Nov. 11, 2026, https://www.microsoft.com/en-us/security/blog/2026/11/11/global-socket-how-threat-actors-weaponizing-gsocket-stealthy-c2/ (source article; telemetry, attack chain, hunting queries, indicators)
  • OTX AlienVault file indicator d94f75a70b5cabaf786ac57177ed841732e62bdcc9a29e06e5b41d9be567bcfa, checked Nov. 12, 2026, https://otx.alienvault.com/indicator/file/d94f75a70b5cabaf786ac57177ed841732e62bdcc9a29e06e5b41d9be567bcfa (MD5 and SHA1)
  • MITRE ATT&CK Enterprise technique pages linked above, MITRE, https://attack.mitre.org/

CVE at a glance

CVE-2026-43284HighPublic exploitLinux
CVSS
8.8 High (v3.1)
EPSS
94.2% chance of exploitation in the next 30 days (higher than 99.8% of CVEs)
Exploited in the wild
Not on CISA’s KEV list
Public exploit
Yes, reported in a Metasploit module, Exploit-DB and 48 GitHub repositories

Full CVE details

Data from NVD, FIRST EPSS and CISA KEV, refreshed automatically. We report whether public exploit code exists but never link to it: fake proof-of-concepts that infect researchers are common.

More from the Roundup