Threat feed

ShadowCloud GitDoor GraphDoor backdoors

Operation ShadowCloud backdoors hide command-and-control inside GitHub, SharePoint and Ably to spy on governments

Posted · Spectrum Delta Research Team

Summary

An espionage campaign tracked as Operation ShadowCloud planted two new backdoors, GitDoor and GraphDoor, on government networks across Southeast Asia, Africa and Central Asia, hiding command-and-control traffic inside GitHub repositories, Microsoft SharePoint sites and the Ably messaging service, Kaspersky reports (B/2). The foothold seen is an abused MeshCentral remote-management agent, probably reusing an existing infection, which drops a loader DLL sideloaded by trusted programs such as Sandboxie Start, OpenJDK javaw, Python and Sysinternals ZoomIt to decrypt GitDoor or GraphDoor in memory. The backdoors pull plug-ins on demand and run COFF shellcode in memory; modules cover keylogging, screenshots, process listing, reverse proxying, a covert SOCKS5 proxy over Ably, credential dumping, browser cookie theft and WhatsApp key recovery, with a confirmed Taiwanese victim and staging observed March to May 2026 on infrastructure prepared since late 2024. Kaspersky notes overlaps with the Chinese-speaking groups FamousSparrow and CopperTurtle, which staged implants in the same directories within one-day windows, but says attribution remains unconfirmed.

Breakdown

Countries

  • Taiwan
  • Southeast Asia
  • Central Asia
  • Africa

Targets

  • Industry: Government

Technical exposure

  • Windows hosts with MeshCentral agent installed
  • Programs vulnerable to DLL sideloading on the host
  • Outbound HTTPS to api.github.com and graph.microsoft.com open
  • Ably messaging and gofile.io reachable from the network

Adversary

Unattributed (Operation ShadowCloud) · Kaspersky GReAT notes overlaps with FamousSparrow and CopperTurtle (B/2)

Procedures (6)

  1. MeshCentral agent beacons to attacker server

    Logs

    • EDR process and network telemetry · meshagent.exe or a MeshCentral service initiating outbound WebSocket traffic to 27.102.66.162 on port 443 with path /agent.ashx, on a host with no sanctioned MeshCentral deployment
    • Firewall or network appliance logs · Repeated TLS sessions to 27.102.66.162:443 from a single internal host, path /agent.ashx, long-lived WebSocket connections

    Detectors

    • Kaspersky Anti Targeted Attack (KATA) · Flags infrequent encrypted connections to unfamiliar external servers, including servers hidden behind content delivery networks
  2. Loader DLL sideloaded by a trusted program

    • T1574.002

    Logs

    • EDR file and image-load telemetry · zoomit.exe started as a Windows service loading WINMM.dll; start.exe loading SbieDll.dll from system32; javaw.exe loading jli.dll; pythonw.exe loading python39.dll; an encrypted config.ini written beside the loader in ProgramData or Program Files staging directories such as excint, sg and PDF24
    • Windows service event logs · Service installation of Sysinternals Screen Magnifier zoomit.exe outside a sanctioned deployment

    Detectors

    • Kaspersky Next EDR Expert · Correlates suspicious endpoint behavior, such as a signed program loading code through a modified configuration file
  3. GitDoor runs command-and-control over GitHub repositories

    • T1071.001Application Layer Protocol: Web Protocols
    • T1102.001Web Service: Dead Drop Resolver

    Logs

    • Web proxy logs · api.github.com calls from non-developer hosts with a random X-CSRF-TOKEN header and Chrome 122.0.6261.96 user agent: POST to /repos/LatonyCharnleyaW/Trix/issues creating issues titled problem [GUID], PUT of files named main.<8-char code>.js.map, and polling of /repos/LatonyCharnleyaW/Havo/contents for command files with extensions kmap, pmap, apmap, swp, tmp

    Detectors

    • Kaspersky Anti Targeted Attack (KATA) · Flags infrequent encrypted connections to unfamiliar external servers, including servers hidden behind content delivery networks
  4. GraphDoor stages commands and data in SharePoint via Microsoft Graph

    • T1071.001Application Layer Protocol: Web Protocols
    • T1102.001Web Service: Dead Drop Resolver

    Logs

    • Web proxy logs · login.microsoftonline.com client-credentials token requests for scope graph.microsoft.com/.default from non-browser processes; graph.microsoft.com PUT of main.<code>.js.map files to buildersemp.sharepoint.com or cskautogo.sharepoint.com; list polling for items titled main.<victim code> with extensions js, swp, tmp, kmap, pmap, apmap
    • Entra ID sign-in logs · App-only service principal authentications to Microsoft Graph from unfamiliar client IPs on tenants that do not use the associated SharePoint sites

    Detectors

    • Kaspersky Anti Targeted Attack (KATA) · Flags infrequent encrypted connections to unfamiliar external servers, including servers hidden behind content delivery networks
  5. Plug-ins keylog, capture screens and list processes in memory

    Logs

    • EDR process and file telemetry · Creation of %APPDATA%\Microsoft\SystemCertificates\Cache\logs.dat with a 32-byte XOR marker; low-level keyboard and mouse hooks; named pipes named p%lu built from a process ID; a ProgramData\Intel_Log directory holding a random GUID; plug-in output strings starting bof-keylogger, bof-process and bof-screenshot
  6. Credentials and browser cookies stolen and exfiltrated

    • T1003.001OS Credential Dumping: LSASS Memory
    • T1539Steal Web Session Cookie

    Logs

    • EDR process telemetry · A credential-dumping module identifying itself as imzimzgo 2.2.0 x64; CookieKatz-based reads of chrome, edge and msedgewebview2 process memory; LSASS access from unusual processes; a WhatsAppKey module and PetitPotam NTLM relay attempts
    • Web proxy logs · File uploads to upload.gofile.io from government workstations outside sanctioned file-transfer use

Indicators of compromise

IPs (6)

  • 27.102.66.162MeshCentral agent command server, WebSocket path /agent.ashx
  • 103.106.230.33proxy C2 resolving to ms.twnic.top, also Cobalt Strike C2
  • 123.58.205.105proxy C2 resolving to ekmt.tw, also Cobalt Strike C2
  • 223.165.4.203proxy server with credentials admin123 / 1qaz@WSX!@#; hunt-only
  • 104.194.154.28proxy server, RouterHosting; 20-plus further proxy IPs listed in Securelist part 2; hunt-only
  • 43.134.62.111proxy server, Tencent cloud ASN; hunt-only

Domains (4)

  • twnic.topCobalt Strike beacon C2 used on GraphDoor-infected hosts
  • ekmt.twCobalt Strike beacon C2 used on GraphDoor-infected hosts
  • buildersemp.sharepoint.comGraphDoor command-and-control site
  • cskautogo.sharepoint.comGraphDoor command-and-control site

URLs (3)

  • wss://27.102.66.162:443/agent.ashxMeshCentral agent command endpoint
  • https://api.github.com/repos/LatonyCharnleyaW/TrixGitDoor upload repository for victim data and results
  • https://api.github.com/repos/LatonyCharnleyaW/HavoGitDoor download repository for commands and plug-ins

Hashes (6)

  • 552f0a9cc5fc3755721fa49be05e8035MD5 GitDoor backdoor
  • 14ec33ea808e697870d00c5e434c2952MD5 GraphDoor backdoor
  • 74b025084026d8d9a64661bf995d835bMD5 MeshCentral agent dropper
  • 32151547d912488ac5242731057170a3MD5 Type 1 loader DLL
  • e63ec733393e4e7e3424cbff918003a3MD5 Type 2 loader SbieDll_st.dll producing GitDoor
  • 91bee19d31d32346cd4d1febb4308606MD5 WINMM.dll loader sideloaded by zoomit.exe

Sources

Questions, detections or sightings of ShadowCloud GitDoor GraphDoor backdoors? Bring them to the community.