Protect.Computer
NEWS

Operation ShadowCloud: Backdoors Hide C2 in GitHub and SharePoint

· 2 min read · Got hacked Network safety
Operation ShadowCloud: Backdoors Hide C2 in GitHub and SharePoint

Kaspersky’s GReAT team has published a two-part analysis of Operation ShadowCloud, an active intrusion campaign it identified in early 2026. The attackers abuse the legitimate MeshCentral remote-management agent (MeshAgent) to drop two previously undocumented backdoors, GitDoor and GraphDoor, which are named for the cloud service each uses for command and control (C2): GitHub for GitDoor, Microsoft SharePoint (through the Microsoft Graph API) for GraphDoor. Kaspersky says the traffic blends into ordinary cloud use, which helps it evade network-based detection, and it found victims in Asia and Africa, primarily in government.

The two backdoors are modular. Both fetch plug-ins on demand and run shellcode directly in memory, and the operators proxy traffic with a modified Erfrp client and an Ably messaging-service plug-in. In the case Kaspersky examined, at a Taiwanese organization, the MeshAgent contacted a hard-coded server and pulled a legitimate executable for DLL sideloading, a rogue loader DLL and an encrypted payload. How the agent first got onto the host is unknown; Kaspersky says the evidence points to reuse of an earlier infection already on the network. GitDoor takes commands from a public GitHub repository and returns results to a private one, and repository creation dates suggest preparation since at least the end of 2024. The Hacker News, summarizing the report, lists 26 GitDoor commands and shellcode modules that can log keystrokes, dump Chrome and Edge cookies from process memory (through CookieKatz), dump Windows LSASS credentials with Mimikatz, take screenshots, extract WhatsApp’s database key and create user accounts. The attacker is unidentified. Kaspersky says some victim systems also held implants from FamousSparrow and CopperTurtle (BlackTech) within a day of GitDoor’s deployment, which it says does not prove a link but suggests a Chinese-speaking group may be developing or using the tools; The Hacker News adds an overlap with Sophos’s “Bronze Sandcastle” activity.

How to check if you’re affected

Affected products are Windows systems that run a MeshCentral Agent you did not deploy, or that match the artifacts below. Kaspersky found victims primarily in government networks in Asia and Africa. From Kaspersky’s report and The Hacker News:

  • Inventory MeshCentral/MeshAgent installs and treat any unexpected one as suspect. Kaspersky’s sample agent was hard-coded to the C2 server 27[.]102[.]66[.]162 (port 443, agent.ashx), and it lists upload.gofile[.]io among the cloud storage services seen.
  • Look for legitimate binaries running alongside unexpected DLLs. Kaspersky’s lists include start.exe, javaw.exe, pythonw.exe and zoomit.exe as sideloaded hosts, with loader DLLs named jli.dll, SbieDll.dll, python39.dll, WINMM.dll and libcef.dll (the DLL names are as listed by The Hacker News).
  • Check for the keystroke log %APPDATA%\Microsoft\SystemCertificates\Cache\logs.dat and, for GraphDoor, a directory named Intel_Log in the Application Data folder.
  • Review outbound connections to GitHub, Microsoft Graph and Ably from servers or workstations that have no business reason to use them. Kaspersky lists nine GitHub accounts as indicators, including LatonyCharnleyaW (repositories Havo and Trix), and gives file hashes for the agent, loaders, payloads and backdoors; compare against the full indicator list in its report.
  • If anything matches, treat credentials and browser sessions on that host as exposed, given the credential and cookie theft modules the report describes.

Our note, not Kaspersky’s: because the traffic uses legitimate cloud services, the report’s indicators are a more practical starting point than blocking those services.

Sources

Related reading