CTIPilot
AI-generated · no human review · verify critical claims against the linked source. how it works →

GSocket

tool · tool:gsocket single-source

Open-source remote access tool that pairs a host and an operator by a shared secret through a public relay, both connecting outbound; Microsoft sees several unrelated actors install it on Linux web servers after exploiting a web application so that access outlives the patch (Microsoft, 2026-11-11).

Aliases: gs-netcat, Global Socket

Coverage
3
1 about it · 2 mentions · first 2026-07-19 → last 2026-11-12
Latest activity
2026-11-12
Microsoft: GSocket relay clients on exploited Linux web servers survive the patch; hunt the host, not the app
Peak priority
notable
1 notable
Targets
·
no sector or region stated
Sources cited
5
5 hosts
2026-07-193 appearances2026-11-12

Defender insights

What each entry about GSocket tells a defender to do, newest first.

2026-11-12NOTABLEMicrosoft: GSocket relay clients on exploited Linux web servers survive the patch; hunt the host, not the app

Exposure · triage · detection

Story timeline

Every entry that names GSocket, newest first. Rows tagged mention only name it in passing: they are listed for completeness and add nothing to the action items, pivots or ATT&CK profile on this page.

  1. 2026-11-12GSocket on compromised Linux web servers: Microsoft sees several unrelated actors install the open-source relay client after exploiting an internet-facing web application, so access outlives the patch; no inbound listener, no attacker-hosted infrastructure
    active-threatsMicrosoft: GSocket relay clients on exploited Linux web servers survive the patch; hunt the host, not the app
  2. 2026-10-16CL-UNK-1211: an AI-assisted intrusion set against government Linux web and mail servers persists through PHP auto_prepend_file, steals sudo passwords with a fake prompt and reads mail stores, and tries to pass as a red-team exercise
    mentionactive-threatsUnit 42: government Linux web and mail hosts hit with PHP prepend persistence, a sudo password trap and mail searches
  3. 2026-07-19ClickLock Stealer, a macOS ClickFix infostealer that force-kills every visible app until the victim types their login password
    mentiondeep-diveClickLock: a modular macOS stealer that locks the desktop by killing every app until the user surrenders their password; Europe is the top victim region

Hunting pivots

ATT&CK techniques (15 across 7 tactics)

15 techniques observed across 1 entry about this entity, derived from entry metadata and body evidence, never asserted without a published entry behind it · pinned to MITRE ATT&CK v20.1 · compare on the matrix · Navigator layer (JSON)

  • Initial AccessExploit Public-Facing Application
  • ExecutionScheduled Task/Job: Cron · Command and Scripting Interpreter: Unix Shell
  • PersistenceScheduled Task/Job: Cron · Create or Modify System Process: Systemd Service · Event Triggered Execution: Unix Shell Configuration Modification
  • Privilege EscalationScheduled Task/Job: Cron · Exploitation for Privilege Escalation · Create or Modify System Process: Systemd Service · Event Triggered Execution: Unix Shell Configuration Modification
  • StealthMasquerading: Overwrite Process Arguments · Indicator Removal: File Deletion · Indicator Removal: Timestomp · Hide Artifacts: Hidden Files and Directories
  • Defense ImpairmentFile and Directory Permissions Modification: Linux and Mac Permissions
  • Command and ControlProxy: External Proxy · Ingress Tool Transfer · Remote Access Tools · Encrypted Channel

Initial Access TA0001

T1190Exploit Public-Facing Application×1

Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network. The weakness in the system can be a software bug, a temporary glitch, or a misconfiguration.

Evidence: 2026-11-12/gsocket-relay-client-keeps-access-after-linux-web-patch · ATT&CK page ↗

Execution TA0002

T1053.003Scheduled Task/Job: Cron×1

Adversaries may abuse the <code>cron</code> utility to perform task scheduling for initial or recurring execution of malicious code. The <code>cron</code> utility is a time-based job scheduler for Unix-like operating systems. The <code> crontab</code> file contains the schedule of cron entries to be run and the specified times for execution. Any <code>crontab</code> files are stored in operating system-specific file paths.

Evidence: 2026-11-12/gsocket-relay-client-keeps-access-after-linux-web-patch · ATT&CK page ↗

T1059.004Command and Scripting Interpreter: Unix Shell×1

Adversaries may abuse Unix shell commands and scripts for execution. Unix shells are the primary command prompt on Linux, macOS, and ESXi systems, though many variations of the Unix shell exist (e.g. sh, ash, bash, zsh, etc.) depending on the specific OS or distribution. Unix shells can control every aspect of a system, with certain commands requiring elevated privileges.

Evidence: 2026-11-12/gsocket-relay-client-keeps-access-after-linux-web-patch · ATT&CK page ↗

Persistence TA0003

T1053.003Scheduled Task/Job: Cron×1

Adversaries may abuse the <code>cron</code> utility to perform task scheduling for initial or recurring execution of malicious code. The <code>cron</code> utility is a time-based job scheduler for Unix-like operating systems. The <code> crontab</code> file contains the schedule of cron entries to be run and the specified times for execution. Any <code>crontab</code> files are stored in operating system-specific file paths.

Evidence: 2026-11-12/gsocket-relay-client-keeps-access-after-linux-web-patch · ATT&CK page ↗

T1543.002Create or Modify System Process: Systemd Service×1

Adversaries may create or modify systemd services to repeatedly execute malicious payloads as part of persistence. Systemd is a system and service manager commonly used for managing background daemon processes (also known as services) and other system resources. Systemd is the default initialization (init) system on many Linux distributions replacing legacy init systems, including SysVinit and Upstart, while remaining backwards compatible.

Evidence: 2026-11-12/gsocket-relay-client-keeps-access-after-linux-web-patch · ATT&CK page ↗

T1546.004Event Triggered Execution: Unix Shell Configuration Modification×1

Adversaries may establish persistence through executing malicious commands triggered by a user’s shell. User Unix Shells execute several configuration scripts at different points throughout the session based on events. For example, when a user opens a command-line interface or remotely logs in (such as via SSH) a login shell is initiated. The login shell executes scripts from the system (<code>/etc</code>) and the user’s home directory (<code>~/</code>) to configure the environment. All login shells on a system use /etc/profile when initiated. These configuration scripts run at the permission level of their directory and are often used to set environment variables, create aliases, and customize the user’s environment. When the shell exits or terminates, additional shell scripts are executed to ensure the shell exits appropriately.

Evidence: 2026-11-12/gsocket-relay-client-keeps-access-after-linux-web-patch · ATT&CK page ↗

Privilege Escalation TA0004

T1053.003Scheduled Task/Job: Cron×1

Adversaries may abuse the <code>cron</code> utility to perform task scheduling for initial or recurring execution of malicious code. The <code>cron</code> utility is a time-based job scheduler for Unix-like operating systems. The <code> crontab</code> file contains the schedule of cron entries to be run and the specified times for execution. Any <code>crontab</code> files are stored in operating system-specific file paths.

Evidence: 2026-11-12/gsocket-relay-client-keeps-access-after-linux-web-patch · ATT&CK page ↗

T1068Exploitation for Privilege Escalation×1

Adversaries may exploit software vulnerabilities in an attempt to elevate privileges. Exploitation of a software vulnerability occurs when an adversary takes advantage of a programming error in a program, service, or within the operating system software or kernel itself to execute adversary-controlled code. Security constructs such as permission levels will often hinder access to information and use of certain techniques, so adversaries will likely need to perform privilege escalation to include use of software exploitation to circumvent those restrictions.

Evidence: 2026-11-12/gsocket-relay-client-keeps-access-after-linux-web-patch · ATT&CK page ↗

T1543.002Create or Modify System Process: Systemd Service×1

Adversaries may create or modify systemd services to repeatedly execute malicious payloads as part of persistence. Systemd is a system and service manager commonly used for managing background daemon processes (also known as services) and other system resources. Systemd is the default initialization (init) system on many Linux distributions replacing legacy init systems, including SysVinit and Upstart, while remaining backwards compatible.

Evidence: 2026-11-12/gsocket-relay-client-keeps-access-after-linux-web-patch · ATT&CK page ↗

T1546.004Event Triggered Execution: Unix Shell Configuration Modification×1

Adversaries may establish persistence through executing malicious commands triggered by a user’s shell. User Unix Shells execute several configuration scripts at different points throughout the session based on events. For example, when a user opens a command-line interface or remotely logs in (such as via SSH) a login shell is initiated. The login shell executes scripts from the system (<code>/etc</code>) and the user’s home directory (<code>~/</code>) to configure the environment. All login shells on a system use /etc/profile when initiated. These configuration scripts run at the permission level of their directory and are often used to set environment variables, create aliases, and customize the user’s environment. When the shell exits or terminates, additional shell scripts are executed to ensure the shell exits appropriately.

Evidence: 2026-11-12/gsocket-relay-client-keeps-access-after-linux-web-patch · ATT&CK page ↗

Stealth TA0005

T1036.011Masquerading: Overwrite Process Arguments×1

Adversaries may modify a process's in-memory arguments to change its name in order to appear as a legitimate or benign process. On Linux, the operating system stores command-line arguments in the process’s stack and passes them to the `main()` function as the `argv` array. The first element, `argv[0]`, typically contains the process name or path - by default, the command used to actually start the process (e.g., `cat /etc/passwd`). By default, the Linux `/proc` filesystem uses this value to represent the process name. The `/proc/<PID>/cmdline` file reflects the contents of this memory, and tools like `ps` use it to display process information. Since arguments are stored in user-space memory at launch, this modification can be performed without elevated privileges.

Evidence: 2026-11-12/gsocket-relay-client-keeps-access-after-linux-web-patch · ATT&CK page ↗

T1070.004Indicator Removal: File Deletion×1

Adversaries may delete files left behind by the actions of their intrusion activity. Malware, tools, or other non-native files dropped or created on a system by an adversary (ex: Ingress Tool Transfer) may leave traces to indicate to what was done within a network and how. Removal of these files can occur during an intrusion, or as part of a post-intrusion process to minimize the adversary's footprint.

Evidence: 2026-11-12/gsocket-relay-client-keeps-access-after-linux-web-patch · ATT&CK page ↗

T1070.006Indicator Removal: Timestomp×1

Adversaries may modify file time attributes to hide new files or changes to existing files. Timestomping is a technique that modifies the timestamps of a file (the modify, access, create, and change times), often to mimic files that are in the same folder and blend malicious files with legitimate files.

Evidence: 2026-11-12/gsocket-relay-client-keeps-access-after-linux-web-patch · ATT&CK page ↗

T1564.001Hide Artifacts: Hidden Files and Directories×1

Adversaries may set files and directories to be hidden to evade detection mechanisms. To prevent normal users from accidentally changing special files on a system, most operating systems have the concept of a ‘hidden’ file. These files don’t show up when a user browses the file system with a GUI or when using normal commands on the command line. Users must explicitly ask to show the hidden files either via a series of Graphical User Interface (GUI) prompts or with command line switches (<code>dir /a</code> for Windows and <code>ls –a</code> for Linux and macOS).

Evidence: 2026-11-12/gsocket-relay-client-keeps-access-after-linux-web-patch · ATT&CK page ↗

Defense Impairment TA0112

T1222.002File and Directory Permissions Modification: Linux and Mac Permissions×1

Adversaries may modify file or directory permissions/attributes to evade access control lists (ACLs) and access protected files. File and directory permissions are commonly managed by ACLs configured by the file or directory owner, or users with the appropriate permissions. File and directory ACL implementations vary by platform, but generally explicitly designate which users or groups can perform which actions (read, write, execute, etc.).

Evidence: 2026-11-12/gsocket-relay-client-keeps-access-after-linux-web-patch · ATT&CK page ↗

Command and Control TA0011

T1090.002Proxy: External Proxy×1

Adversaries may use an external proxy to act as an intermediary for network communications to a command and control server to avoid direct connections to their infrastructure. Many tools exist that enable traffic redirection through proxies or port redirection, including HTRAN, ZXProxy, and ZXPortMap. Adversaries use these types of proxies to manage command and control communications, to provide resiliency in the face of connection loss, or to ride over existing trusted communications paths to avoid suspicion.

Evidence: 2026-11-12/gsocket-relay-client-keeps-access-after-linux-web-patch · ATT&CK page ↗

T1105Ingress Tool Transfer×1

Adversaries may transfer tools or other files from an external system into a compromised environment. Tools or files may be copied from an external adversary-controlled system to the victim network through the command and control channel or through alternate protocols such as ftp. Once present, adversaries may also transfer/spread tools between victim devices within a compromised environment (i.e. Lateral Tool Transfer).

Evidence: 2026-11-12/gsocket-relay-client-keeps-access-after-linux-web-patch · ATT&CK page ↗

T1219Remote Access Tools×1

An adversary may use legitimate remote access tools to establish an interactive command and control channel within a network. Remote access tools create a session between two trusted hosts through a graphical interface, a command line interaction, a protocol tunnel via development or management software, or hardware-level access such as KVM (Keyboard, Video, Mouse) over IP solutions. Desktop support software (usually graphical interface) and remote management software (typically command line interface) allow a user to control a computer remotely as if they are a local user inheriting the user or software permissions. This software is commonly used for troubleshooting, software installation, and system management. Adversaries may similarly abuse response features included in EDR and other defensive tools that enable remote access.

Evidence: 2026-11-12/gsocket-relay-client-keeps-access-after-linux-web-patch · ATT&CK page ↗

T1573Encrypted Channel×1

Adversaries may employ an encryption algorithm to conceal command and control traffic rather than relying on any inherent protections provided by a communication protocol. Despite the use of a secure algorithm, these implementations may be vulnerable to reverse engineering if secret keys are encoded and/or generated within malware samples/configuration files.

Evidence: 2026-11-12/gsocket-relay-client-keeps-access-after-linux-web-patch · ATT&CK page ↗

Entries about GSocket (1)

2026-11-12 · view entry permalink →

NOTABLENATOB2

GSocket on compromised Linux web servers: Microsoft sees several unrelated actors install the open-source relay client after exploiting an internet-facing web application, so access outlives the patch; no inbound listener, no attacker-hosted infrastructure

Microsoft observed several unrelated threat actors deploy GSocket, an open-source remote access tool, on Linux servers after exploiting an internet-facing web application, and says it kept access after the exploited vulnerabilities were remediated (Microsoft, 2026-11-11). The chain starts with command execution as a child of the web server or application runtime, where curl fetches an installation script that bash runs; the script profiles the host, picks a client matching the architecture, stages it as a hidden, executable file in a writable or memory-backed path such as /dev/shm and opens encrypted outbound command and control through the Global Socket Relay Network (Microsoft, 2026-11-11). The client is then disguised with kernel-thread-like process names (bash exec -a), persisted through cron, systemd units, shell profiles, watchdogs and redundant copies, and the staging files are removed (Microsoft, 2026-11-11). In a few incidents the actors afterwards attempted the Linux kernel flaw CVE-2026-43284, known as Dirty Frag, to reach root; Microsoft gives no success statement and no affected or fixed versions (Microsoft, 2026-11-11).

Both the compromised host and the operator connect outbound to the public relay, so the host needs no inbound listener, inbound firewall rules do not see the traffic and a shared secret, not an address, pairs the endpoints, which lets the operator reconnect later from any compatible client; Microsoft therefore says that blocking an address or domain is unlikely to cut off access, while egress filtering and outbound monitoring can see it (Microsoft, 2026-11-11). Microsoft's telemetry is concentrated on web applications and hosting; education and research and technology and telecommunications were the largest shares of affected organisations, which Microsoft says reflect exposure more likely than deliberate sector selection (Microsoft, 2026-11-11).

Triage: Microsoft notes that the same relay model also serves legitimate remote administration, and says a match must be judged on process ancestry, execution context, persistence changes and related network activity; a client started from a web-service process tree, from a writable or memory-backed path and under a kernel-thread-like name is the pattern it describes (Microsoft, 2026-11-11).

Threat actors used Gsocket to maintain access even after the vulnerabilities used for initial compromise were remediated.

Because GSocket runs independently of the exploited application, patching the vulnerability does not remove the relay client or its persistence.

Microsoft Threat Intelligence 2026-11-11

Builds on: Dirty Frag: two kernel page-cache write flaws give local root; Microsoft saw su escalation that…

threat12 Nov 04:06Zsingle-sourceOpen finding →

Co-occurring entities

Derived: referenced by the same focused operational entries (weekly summaries and report roundups don't count); ×N counts the shared entries.

Where this entity is cited

  • Threats2
  • Deep dive1

Source distribution

  • bleepingcomputer.com1 (20%)
  • forbes.com1 (20%)
  • group-ib.com1 (20%)
  • microsoft.com1 (20%)
  • unit42.paloaltonetworks.com1 (20%)