"The threat actor behind it is abusing the legitimate MeshAgent utility to drop two brand-new backdoors," Kaspersky researchers Saurabh Sharma and Noushin Shabab said.
Operation ShadowCloud: scope, timeline, and targets
Kaspersky has codenamed the activity Operation ShadowCloud after identifying an active intrusion campaign in early 2026 that delivered two previously undocumented backdoors. The campaign has targeted government sectors in Asia and Africa and used legitimate cloud services to mask command‑and‑control (C2) traffic, according to the company's two‑part analysis.
Kaspersky reports that preparations for the campaign extend back to at least the end of 2024 based on repository creation dates tied to the malware's GitHub infrastructure. The report does not publicly name specific victim organizations beyond an unspecified Taiwanese organization where the initial MeshCentral Agent was observed, nor does it identify the actor responsible; Kaspersky notes only tactical overlap with activity tracked by others under China‑nexus labels.
Initial access: MeshCentral Agent, hard‑coded C2, and staged payloads
The starting point for the intrusions has been traced to a MeshCentral Agent, a legitimate remote administration utility. The MeshCentral Agent in these incidents was configured to contact a hard‑coded WebSocket C2 endpoint at "wss://27.102.66[.]162:443/agent.ashx" and then fetch three payloads staged on the endpoint:
- a legitimate binary used for DLL sideloading (examples: start.exe, pythonw.exe, zoomit.exe);
- a rogue loader DLL that unpacks and executes the next stage (examples: jli.dll, SbieDll.dll, python39.dll, WINMM.dll, libcef.dll); and
- an encrypted file containing the core payload.
Kaspersky identified at least two distinct DLL loader types. Loader (Type 1) decodes the encrypted payload using an RC4 stream cipher followed by an XOR mask; Loader (Type 2) uses straight XOR decoding. Both loaders ultimately inject the decrypted backdoor into the current process memory to run without touching disk in its final form.

Nobody's watching your logs at 2 AM.
Full SOC coverage without building one. Nubivance deploys and manages Rapid7 InsightIDR and MDR for organizations that need detection and response, not another dashboard.
Get coverageGitDoor: GitHub as a covert C2 channel and a 26‑command toolkit
One of the implants, dubbed GitDoor, uses GitHub for C2. The malware polls two repositories for instructions and result exfiltration: a public repository at "/repos/LatonyCharnleyaW/Havo" for receiving command payloads and a private repository at "/repos/LatonyCharnleyaW/Trix" for uploading execution results. Kaspersky's timeline ties those repositories to planning that began no later than the end of 2024.
GitDoor supports 26 commands. Among its capabilities are file management, keystroke logging, launching a proxy (including via the Ably messaging service), and loading shellcode packaged as Base64‑encoded COFF binaries. The custom shellcode feature downloads modules that enable process injection (including APC injection), Windows service enumeration and management, recursive file and directory deletion, network activity enumeration, process memory dumping, command execution via "cmd.exe", scheduled task management, Registry enumeration and modification, user and group enumeration and manipulation, screenshot capture, credential theft via Mimikatz, and targeted data extraction such as Chrome/Edge cookies via CookieKatz and WhatsApp database decryption keys.
GitDoor stores keystroke logs at "%APPDATA%\\Microsoft\\SystemCertificates\\Cache\\logs.dat" and can initiate NTLM authentication to attacker‑controlled endpoints and calculate system idle time by examining mouse and keyboard input.
GraphDoor: Microsoft Graph, SharePoint staging, and Ably proxying
The second implant, GraphDoor, uses Microsoft's cloud ecosystem for C2. It opens a named pipe, creates an "Intel_Log" directory under the system Application Data folder, and compiles system information to send back to attackers. To communicate, GraphDoor authenticates through "login.microsoftonline.com" on port 443, uses the resulting access token to call the Microsoft Graph API, and stages data on a SharePoint drive.
GraphDoor fetches three plugin modules and launches them in parallel to perform screenshot capture, process listing, and keylogging. Its plugin set also includes moveDir.ts (to relocate the legitimate executable, the malicious loader DLL, and the encrypted backdoor file), channel.ts (to launch a proxy), abchannel.ts (to proxy traffic via Ably), and ab2channel.ts (a covert SOCKS5 proxy that tunnels TCP traffic through Ably's Pusher‑compatible WebSocket service). The implant logs keystrokes to the same file path used by GitDoor ("%APPDATA%\\Microsoft\\SystemCertificates\\Cache\\logs.dat") and extends GitDoor's shellcode abilities with two additional commands to run MZ executables and to execute commands via "cmd.exe".
What this means for technologists, policymakers, and affected enterprises
Technologists and security teams should note the deliberate use of cloud APIs and messaging services—Microsoft Graph, SharePoint, GitHub, and Ably—to blend malicious C2 with legitimate enterprise traffic, complicating network‑based detection and allowing on‑demand delivery of plugins and shellcode without modifying host files. Detection strategies that rely solely on anomalous network endpoints may be insufficient when cloud API calls appear indistinguishable from normal usage.
Policymakers and procurement leaders responsible for enterprise cloud hygiene will see two concrete pressures: the risk of legitimate administration tooling being abused for persistence and the need to review access‑token flows and cloud‑storage usage patterns. GraphDoor's authentication through "login.microsoftonline.com" and staging via SharePoint underline that token lifecycle and app‑permission monitoring are critical controls.
Affected enterprises — especially the government sectors cited in Asia and Africa and the unnamed Taiwanese organization where MeshCentral was observed — must assume that intruders can deploy modular backdoors capable of keystroke logging, credential theft (Mimikatz), process injection, and remote proxying via third‑party messaging services. The observation that other implants from groups tracked under Bronze Sandcastle, FamousSparrow, and CopperTurtle shared staging directories within a one‑day window of GitDoor deployment suggests opportunistic reuse of compromised environments.
Operation ShadowCloud demonstrates a deliberate move to weaponize mainstream developer and collaboration platforms as C2 infrastructure and to strand defenders between legitimate cloud telemetry and covert implant behavior. Kaspersky's analysis leaves open how the MeshCentral Agent was first installed; it does show, however, a clear operational pattern: reuse of legitimate tooling, layered loader decoding (RC4+XOR or XOR), and cloud‑based, pluginized persistence.
Full original analysis: https://thehackernews.com/2026/11/new-gitdoor-and-graphdoor-backdoors.html




