<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:webfeeds="http://webfeeds.org/rss/1.0"><channel><title>Gsocket - CraftedSignal Threat Feed</title><link>https://feed.craftedsignal.io/tags/gsocket/</link><description>Trending threats, MITRE ATT&amp;CK coverage, and detection metadata. Fed continuously.</description><generator>Hugo</generator><language>en</language><managingEditor>hello@craftedsignal.io</managingEditor><webMaster>hello@craftedsignal.io</webMaster><lastBuildDate>Wed, 11 Nov 2026 21:35:25 +0000</lastBuildDate><atom:link href="https://feed.craftedsignal.io/tags/gsocket/feed.xml" rel="self" type="application/rss+xml"/><image><url>https://feed.craftedsignal.io/favicon-32x32.png</url><title>CraftedSignal Threat Feed</title><link>https://feed.craftedsignal.io/</link><width>32</width><height>32</height></image><webfeeds:icon>https://feed.craftedsignal.io/favicon.svg</webfeeds:icon><item><title>Threat actors weaponizing GSocket for persistent C2 on Linux servers</title><link>https://feed.craftedsignal.io/briefs/2026-11-gsocket-weaponization/</link><pubDate>Wed, 11 Nov 2026 21:35:25 +0000</pubDate><author>hello@craftedsignal.io</author><guid isPermaLink="true">https://feed.craftedsignal.io/briefs/2026-11-gsocket-weaponization/</guid><description>Threat actors are increasingly deploying the legitimate GSocket tool on compromised Linux servers to maintain persistent, encrypted remote access that survives the remediation of initial RCE vulnerabilities.</description><content:encoded><![CDATA[<p>Threat actors are leveraging GSocket, an open-source remote access tool, to maintain persistent, encrypted command-and-control (C2) channels on compromised Linux systems. This technique allows attackers to retain access even after the initial entry-point vulnerability (such as a web application RCE) has been patched. GSocket operates by establishing outbound connections to a public Global Socket Relay Network, bypassing traditional inbound firewall rules and eliminating the need for attacker-controlled C2 infrastructure.</p>
<h2 id="attack-chain">Attack Chain</h2>
<ol>
<li>Initial Access: Threat actors exploit a remote code execution (RCE) vulnerability in an internet-facing application (e.g., PHP-based applications, cPanel, or Apache).</li>
<li>Profiling: The attacker executes commands to profile the system architecture and environment.</li>
<li>Tool Transfer: Using curl or similar utilities, the attacker downloads a GSocket deployment script.</li>
<li>Staging: The script stages the GSocket binary in temporary or memory-backed directories such as /dev/shm to conceal the file.</li>
<li>Execution: The GSocket client is executed, establishing an encrypted outbound connection to the Global Socket Relay Network.</li>
<li>C2 Establishment: The relay bridges the connection between the host and the operator, allowing for persistent, interactive access.</li>
<li>Persistence: The attacker installs persistent mechanisms to survive system reboots.</li>
</ol>
<h2 id="impact">Impact</h2>
<p>This technique enables persistent post-compromise access that remains active after the original vulnerability is remediated. The use of a public relay network makes it difficult for defenders to identify malicious activity based solely on traditional IP or domain-based egress blocking.</p>
<h2 id="recommendation">Recommendation</h2>
<ul>
<li>Implement egress filtering to restrict unauthorized outbound connections to known public relay networks.</li>
<li>Monitor for unauthorized execution of binaries from temporary locations such as /dev/shm.</li>
<li>Audit for suspicious process names and persistence mechanisms commonly associated with remote access tools.</li>
<li>Treat the discovery of GSocket on a host as a sign of a persistent compromise, necessitating deeper incident response beyond simply patching the initial entry-point.</li>
</ul>
]]></content:encoded><category domain="severity">high</category><category domain="type">advisory</category><category>c2</category><category>linux</category><category>gsocket</category><category>persistence</category><category>persistence-mechanism</category></item></channel></rss>