<?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/"><channel><title>C2 — CraftedSignal Threat Feed</title><link>https://feed.craftedsignal.io/tags/c2/</link><description>Trending threats, MITRE ATT&amp;CK coverage, and detection metadata — refreshed continuously.</description><generator>Hugo</generator><language>en</language><managingEditor>hello@craftedsignal.io</managingEditor><webMaster>hello@craftedsignal.io</webMaster><lastBuildDate>Sat, 21 Mar 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://feed.craftedsignal.io/tags/c2/feed.xml" rel="self" type="application/rss+xml"/><item><title>China-Nexus Campaign Using Google Calendar as C2</title><link>https://feed.craftedsignal.io/briefs/2026-03-calendar-c2/</link><pubDate>Sat, 21 Mar 2026 00:00:00 +0000</pubDate><author>hello@craftedsignal.io</author><guid isPermaLink="true">https://feed.craftedsignal.io/briefs/2026-03-calendar-c2/</guid><description>A China-nexus threat actor is utilizing Google Calendar as a command and control (C2) infrastructure to conduct stealthy operations.</description><content:encoded><![CDATA[<p>A China-nexus threat actor has been observed leveraging Google Calendar as a novel command and control (C2) mechanism. This campaign, observed starting in 2025, uses calendar entries to relay commands to compromised hosts. The use of Google Calendar allows the attacker to blend in with legitimate network traffic, evade traditional C2 detection methods, and maintain persistence. The stealthy nature of this approach makes it difficult to detect and attribute. This technique is particularly concerning because it leverages a common and trusted service, making it harder to differentiate between legitimate and malicious activity. The scope of targeting is currently unknown, but the use of advanced C2 infrastructure suggests a sophisticated and potentially widespread campaign.</p>
<h2 id="attack-chain">Attack Chain</h2>
<ol>
<li>Initial compromise occurs through an unknown vector, potentially exploiting vulnerabilities or using social engineering.</li>
<li>A lightweight agent is installed on the target system. This agent is responsible for interacting with the Google Calendar API.</li>
<li>The agent authenticates to a pre-configured Google account controlled by the attacker using stolen or pre-configured credentials.</li>
<li>The agent periodically polls the Google Calendar API for new calendar events.</li>
<li>The attacker creates calendar events containing base64-encoded commands.</li>
<li>The agent retrieves the calendar event, decodes the command, and executes it on the compromised system.</li>
<li>The agent transmits the results of the executed command back to the attacker, potentially through another Google service or a separate channel.</li>
<li>The attacker uses the C2 channel to perform further actions, such as lateral movement, data exfiltration, or deployment of additional malware.</li>
</ol>
<h2 id="impact">Impact</h2>
<p>Compromised systems could be leveraged for a variety of malicious activities, including data theft, espionage, and disruption of services. The use of Google Calendar as a C2 channel makes attribution challenging and allows the attacker to maintain a persistent presence on the compromised network. Successful attacks could lead to significant financial losses, reputational damage, and loss of sensitive information. The number of victims and specific sectors targeted are currently unknown.</p>
<h2 id="recommendation">Recommendation</h2>
<ul>
<li>Monitor API calls to <code>googleapis.com</code> for unusual patterns or unauthorized access attempts, specifically looking for calendar event modifications from unusual user agents (reference: Attack Chain step 4).</li>
<li>Implement the Sigma rule to detect processes making modifications to Google Calendar.</li>
<li>Enable and review Google Workspace audit logs for suspicious calendar activity, including event creation and modification from unexpected locations or accounts (reference: Attack Chain step 5).</li>
</ul>
]]></content:encoded><category domain="severity">high</category><category domain="type">threat</category><category>google-calendar</category><category>c2</category><category>china-nexus</category></item><item><title>Iranian Botnet Operation Exposed via Open Directory</title><link>https://feed.craftedsignal.io/briefs/2024-01-iranian-botnet/</link><pubDate>Tue, 17 Mar 2026 19:15:28 +0000</pubDate><author>hello@craftedsignal.io</author><guid isPermaLink="true">https://feed.craftedsignal.io/briefs/2024-01-iranian-botnet/</guid><description>An Iranian botnet operation utilizing a 15-node relay network and active C2 infrastructure was exposed through an open directory.</description><content:encoded><![CDATA[<p>A blog post on hunt.io details an Iranian botnet operation discovered through an open directory. The operation involves a 15-node relay network, suggesting a focus on obfuscation and resilience. The existence of an active Command and Control (C2) infrastructure indicates ongoing malicious activity. The exposure of these details allows defenders to gain insights into the botnet&rsquo;s architecture and potentially disrupt its operations. While the specific targeting and malware used remain unclear from this report, the network structure points to a potentially sophisticated actor capable of conducting sustained campaigns. Understanding the C2 communication patterns and relay node infrastructure is crucial for effective defense.</p>
<h2 id="attack-chain">Attack Chain</h2>
<ol>
<li>Initial Compromise: Systems are compromised through an unknown initial access vector.</li>
<li>Bot Installation: A bot payload is installed on the compromised systems.</li>
<li>C2 Communication: The bots establish communication with the C2 server to receive commands.</li>
<li>Relay Network Activation: Bots connect to one another creating the 15-node relay network.</li>
<li>Command Execution: The C2 server issues commands to the bots through the relay network.</li>
<li>Malicious Activity: Bots execute malicious commands, the specific actions are currently unknown.</li>
</ol>
<h2 id="impact">Impact</h2>
<p>The impact of this botnet is currently unknown due to limited information, but botnets are commonly used for DDoS attacks, spam campaigns, or credential stuffing. If the botnet successfully conducts its objectives it could lead to service disruptions, data breaches, or further compromise of systems within targeted networks. The Iranian origin suggests potential geopolitical motivations.</p>
<h2 id="recommendation">Recommendation</h2>
<ul>
<li>Monitor network traffic for connections to the domain <code>hunt.io</code> as it is related to the botnet operation ([IOC: hunt.io]).</li>
<li>Implement a network connection rule to detect unusual network connections that could indicate the C2 activity or relay network behavior.</li>
<li>Investigate any systems that show signs of unusual network activity or communication with external domains.</li>
</ul>
]]></content:encoded><category domain="severity">medium</category><category domain="type">advisory</category><category>botnet</category><category>iran</category><category>C2</category></item></channel></rss>