Kaspersky reports GitDoor and GraphDoor backdoors using GitHub, SharePoint C2
The Hacker News reports Kaspersky found GitDoor and GraphDoor backdoors using GitHub and SharePoint for C2; check logs for the listed indicators.
- Published
- Exploitation
- Yes, according to Kaspersky as reported by The Hacker News, an active campaign against government sectors in Asia and Africa; not independently verified
What happened
The Hacker News reports that Kaspersky has described an active intrusion campaign, which it codenamed Operation ShadowCloud, against government sectors in Asia and Africa. According to The Hacker News, Kaspersky says it identified the campaign in early 2026 and that the attackers abuse the legitimate MeshAgent utility to drop two previously undocumented backdoors, GitDoor and GraphDoor. These claims come from Kaspersky via The Hacker News; the sources do not show independent verification.
Kaspersky says the backdoors hide command-and-control (C2) traffic behind Microsoft SharePoint, GitHub and Ably. It says this lets the traffic blend in with normal cloud API traffic and evade many network-based detections. The Hacker News reports the following details, attributed to Kaspersky:
- The attack starts from a MeshCentral Agent configured to contact the hard-coded C2 address wss://27.102.66[.]162:443/agent.ashx. It then fetches a legitimate binary for DLL sideloading, a rogue loader DLL and an encrypted payload file.
- The sideloading binaries named are start.exe, pythonw.exe and zoomit.exe. The loader DLLs named are jli.dll, SbieDll.dll, python39.dll, WINMM.dll and libcef.dll.
- GitDoor uses GitHub for C2, with two repositories: “/repos/LatonyCharnleyaW/Havo” (public) for commands and “/repos/LatonyCharnleyaW/Trix” (private) for results. Kaspersky says the repository creation dates suggest preparation since at least the end of 2024. GitDoor supports 26 commands, including file management, keystroke logging and proxying.
- Kaspersky says GitDoor’s shellcode modules cover credential and cookie theft (Mimikatz against LSASS, CookieKatz for Chrome and Edge cookies), screenshots, scheduled task and registry changes, and adding Windows user accounts.
- GraphDoor creates a directory named “Intel_Log” in the Application Data folder. It authenticates through login.microsoftonline.com with a malicious application and uses the Microsoft Graph API to stage data on a SharePoint drive. It fetches plugins for keylogging, process listing, screenshots and proxying through Ably.
- Both backdoors reportedly log keystrokes to “%APPDATA%\Microsoft\SystemCertificates\Cache\logs.dat”.
Attribution is not established. Kaspersky says the actor’s identity is unknown. It reports some overlap with activity Sophos tracks as Bronze Sandcastle, and tactical similarities with FamousSparrow and CopperTurtle (aka BlackTech). Kaspersky says this “does not prove a direct link” but suggests a Chinese-speaking group may be developing or using the backdoors.
Not confirmed in the source: how MeshAgent reaches the host (Kaspersky points to “reuse of a prior infection already present on the network”), the number of victims, which organizations beyond one unspecified Taiwanese target were hit, and any file hashes or vendor mitigation guidance.
Am I affected?
Per Kaspersky, the reported targets are government sectors in Asia and Africa, and one unspecified Taiwanese organization is named. Whether other sectors or regions are affected is not confirmed.
You may want to check your environment if any of the following applies:
- A MeshCentral Agent or MeshAgent is present that your IT team did not deploy.
- Hosts show the file names, the “Intel_Log” directory or the logs.dat path listed above.
- Systems or proxies have connected to the C2 address above.
- Network or code-hosting logs show access to the GitHub repositories named above.
The source gives no detection signatures, so absence of these artifacts does not prove a system is clean.
What to do now
- Inventory MeshCentral Agent installs and remove or investigate any you did not authorize. The source says the campaign starts from this legitimate tool.
- Search endpoints for the sideloading binaries and loader DLL names above, particularly outside their normal install locations. This is a suggested hunt based on the listed indicators, not guidance from Kaspersky.
- Search for the “Intel_Log” directory and the “%APPDATA%\Microsoft\SystemCertificates\Cache\logs.dat” file.
- Search proxy and DNS logs for connections to 27.102.66[.]162 and for requests to the GitHub paths “/repos/LatonyCharnleyaW/Havo” and “/repos/LatonyCharnleyaW/Trix”.
- Review Microsoft Entra sign-ins and application registrations for unfamiliar applications that use the Graph API, since GraphDoor reportedly authenticates through login.microsoftonline.com with a malicious application. This is a suggested review, not sourced guidance.
- If you find a match, treat the host as potentially compromised. Kaspersky describes credential dumping and cookie theft capabilities, so consider the credentials and sessions reachable from that host. Follow your own incident response process.
- Read the full two-part Kaspersky analysis for further indicators. The Hacker News article quotes it but does not link a primary report in the text provided.