
Operation ShadowCloud uses GitHub and SharePoint for espionage
New cyberespionage campaign uses GitDoor and GraphDoor backdoors, abusing legitimate cloud services to hide C2 traffic.
Kaspersky researchers revealed findings about an active cyberespionage campaign dubbed Operation ShadowCloud. The threat targets government organizations in regions of Africa, Southeast Asia, and Central Asia, in addition to records indicating an initial scope aimed at entities in Taiwan. The operation employs two previously unseen backdoors, named GitDoor and GraphDoor, which use legitimate cloud infrastructure services to mask their command and control (C2) communications.
Initial Access Mechanism and Abused Legitimate Tools
The initial infection vector identified by analysts involves the reuse of pre-existing network accesses or the exploitation of already compromised infrastructures, where operators deploy the legitimate utility MeshCentral Agent. Although the agent is widely used for remote administration and IT support, it is instrumentalized to connect to a hardcoded C2 server and download a set of three stage files to the compromised endpoint: a legitimate binary used for DLL sideloading, a malicious loader DLL, and an encrypted file containing the main payload.
Different types of loaders have been documented in the campaign. Loader Type 1 employs a hybrid scheme using the RC4 stream cipher followed by an XOR mask, while Loader Type 2 simplifies the process with a direct XOR operation. These components decrypt and inject the backdoor payload directly into the memory of the running process, hindering detection based on static files.
GitDoor and GraphDoor: Cloud C2 Channels
The modular implants are named according to the cloud platform used for C2 traffic. GitDoor uses GitHub repositories — with public structures for receiving commands and private ones for uploading results — operating with infrastructure prepared since late 2024. The backdoor supports dozens of commands for file management, keylogging, shellcode execution via COFF, and process injection.
In turn, GraphDoor establishes communication through the Microsoft Graph API and the SharePoint service. After authenticating via login.microsoftonline.com, the malware downloads additional modules and plugins (such as kl.ts for keylogging, scr.ts for screen capture, and channel.ts for network tunneling) executed in parallel. The proxy ecosystem in both variants also makes use of the real-time messaging platform Ably to tunnel traffic and confuse perimeter defenses.
Attribution and Operational Complexity
Kaspersky highlighted that Operation ShadowCloud shows tactical and operational overlaps with Chinese-origin threat groups monitored under the pseudonyms Bronze Sandcastle, FamousSparrow, and CopperTurtle (also known as BlackTech). While direct attribution remains under investigation, the reuse of staging directories and technical sophistication indicate an organized group focused on long-term espionage.
The use of legitimate corporate APIs poses a significant challenge for defensive security teams, as traffic generated by GitHub, Microsoft Graph, and Ably perfectly mimics the behavior of everyday enterprise applications, rendering deep packet inspection ineffective without the aid of advanced behavioral telemetry on endpoints.
CyberX Technical Analysis
The architecture of Operation ShadowCloud demonstrates a leap in cloud-based evasion sophistication, utilizing communication channels inherent to modern corporate environments to mask malicious traffic.
Loading and Injection Architecture
The infection process begins with the abuse of MeshCentral Agent, a legitimate remote management utility. The execution chain employs classic DLL sideloading techniques combined with custom loaders that perform in-memory decryption (via RC4/XOR), preventing the writing of clean artifacts to disk and thwarting traditional static analyses. The use of control flow flattening and nested auxiliary functions in the GitDoor and GraphDoor backdoors raises the cost of reverse engineering.
C2 Channels and Transport Layer
The use of platforms like GitHub (via repository API) and Microsoft SharePoint (via Microsoft Graph API) ensures high operational resilience for attackers. Since these requests use standard ports (HTTPS/443) and domains widely trusted by corporate firewalls, next-generation firewalls (NGFWs) and SSL/TLS inspection solutions encounter limitations in distinguishing legitimate API calls from data exfiltration or control commands.
Post-Exploitation Capabilities
Both backdoors operate with an architecture based on dynamically loaded plugins in memory. Capabilities include LSASS credential dumping via Mimikatz, browser cookie extraction with CookieKatz, screen capture, WhatsApp decryption key extraction, and execution of custom SOCKS5 proxies through the Ably service. The absence of reliance on fixed local binaries allows operators to update their arsenal on demand.
CyberX SOC Intelligence Bulletin
Operation ShadowCloud represents an advanced espionage vector focused on governments and strategic entities, requiring deep visibility into endpoints and rigorous monitoring of API calls and connections to third-party cloud services.
Exposure Surface and Affected Assets
Windows environments using remote management tools, government workstations, and servers with access to external repositories and cloud collaboration services form the primary risk surface. Persistence relies on pre-existing administration agents or vulnerabilities that allow the initial binary drop.
Investigation Signals and Recommended Telemetry
- Monitor anomalous executions of legitimate utilities accompanied by the loading of unsigned or renamed DLLs (e.g., sideloading involving
start.exe,pythonw.exe, orzoomit.exe). - Investigate processes generating atypical traffic to the GitHub API, Microsoft Graph API, or Ably endpoints outside the scope of authorized development or administrative use.
- Track the creation of suspicious directories in application profiles, such as the
Intel_Logfolder in the Application Data directory. - Analyze the use of unknown named pipes and the creation of scheduled tasks or services with Base64-encoded command-line parameters.
Verifiable Indicators of Compromise (IoCs)
- MeshCentral Agent C2 server identified in sources:
wss://27.102.66.162:443/agent.ashx - GitHub repositories associated with GitDoor:
/repos/LatonyCharnleyaW/Havo(public) and/repos/LatonyCharnleyaW/Trix(private) - GraphDoor plugin filenames:
kl.ts,pr.ts,scr.ts,moveDir.ts,channel.ts,abchannel.ts,ab2channel.ts - Keystroke log path:
%APPDATA%\Microsoft\SystemCertificates\Cache\logs.dat
Mitigation and Response
Strict auditing of unauthorized remote access tools on the network (such as unsupervised MeshCentral instances), restriction of non-corporate cloud API usage through CASB (Cloud Access Security Broker) policies, and application of EDR rules to detect process injection and anomalous API calls directed at Microsoft Graph and GitHub are recommended.
Frequently asked questions
Why is Operation ShadowCloud difficult to detect?
Operation ShadowCloud is difficult to detect because it abuses legitimate corporate APIs like GitHub and Microsoft Graph, mimicking normal enterprise traffic. These requests use standard ports and trusted domains, limiting the effectiveness of deep packet inspection, NGFWs, and SSL/TLS inspection.
What are the primary risk surfaces for Operation ShadowCloud?
The primary risk surfaces include Windows environments using remote management tools, government workstations, and servers with access to external repositories and cloud collaboration services. Persistence relies on pre-existing administration agents or vulnerabilities.
What are the key capabilities of the GitDoor and GraphDoor backdoors?
The backdoors support dozens of commands for file management, keylogging, shellcode execution, and process injection. They also include capabilities like LSASS credential dumping, browser cookie extraction, screen capture, and execution of custom SOCKS5 proxies.


