As reported by The Hacker News, Kaspersky has disclosed Operation ShadowCloud, an active espionage campaign targeting government entities across Asia and Africa with two novel backdoors—GitDoor and GraphDoor—that route command-and-control traffic through GitHub, Microsoft SharePoint, and Ably. The campaign, identified in early 2026, abuses the legitimate MeshAgent utility as an initial foothold and deploys modular implants designed to disappear into normal cloud traffic.
The significance of this campaign extends well beyond the two new malware families. Operation ShadowCloud is a textbook example of the living-off-trusted-sites paradigm reaching maturity. When C2 traffic is indistinguishable from a developer pulling a repository or a knowledge worker accessing a SharePoint document, traditional network perimeter controls become structurally blind. The threat actor isn't just evading detection—they're weaponizing the implicit trust that security tools grant to major cloud providers.
Why This Matters
The core problem is architectural. Most network security stacks—NGFWs, SWGs, proxy logs—are configured to allow or lightly inspect traffic to github.com, *.sharepoint.com, and real-time messaging APIs like Ably. These destinations carry enormous legitimate volume, making volumetric anomaly detection unreliable. The backdoors' use of in-memory shellcode execution and modular plugin architecture further minimizes host-based artifacts.
Equally concerning is the initial access vector. Kaspersky notes the MeshCentral Agent was likely already present on the target network—a reuse of prior infection. This highlights a persistent gap in incident response: organizations contain but don't fully eradicate. Surviving implants from previous campaigns become staging grounds for more sophisticated follow-on intrusions.
Who Is at Risk
Broader Implications
The operational challenge is no longer identifying malicious domains—it's identifying malicious behavior on domains you must allow.
This campaign reinforces a trend we've tracked across multiple APT groups: C2 infrastructure is migrating from purpose-built servers to consumer-grade cloud platforms. GitDoor and GraphDoor are modular and extensible, meaning we should expect variants targeting GitLab, Bitbucket, Notion, Slack, and other trusted services in the near term. Defenders need detection logic that doesn't break every time the threat actor swaps the SaaS frontend.
Shield53 Recommendations
- Audit RMM tooling: Inventory all remote management agents across the estate. Investigate any MeshCentral, MeshAgent, or similar utility that cannot be attributed to a sanctioned IT workflow. Treat unexpected RMM binaries as high-priority incidents.
- Implement context-aware cloud egress monitoring: Deploy EDR or NDR that can correlate process identity with outbound TLS destinations. A
pythonw.exeorzoomit.exeprocess communicating with GitHub or SharePoint APIs is anomalous and should trigger immediate review. - Hunt for DLL sideloading patterns: The loaders identified (jli.dll, SbieDll.dll, python39.dll, WINMM.dll, libcef.dll) loaded by legitimate binaries (start.exe, pythonw.exe, zoomit.exe) are classic sideloading indicators. Query EDR telemetry for signed binaries loading unsigned or unexpectedly located DLLs.
- Constrain outbound SaaS access: Where feasible, restrict GitHub and SharePoint API access to known corporate identities and enforce via authenticated proxy. Monitor for OAuth token abuse and anomalous API call patterns.
- Re-examine past incidents: If your organization has suffered a prior compromise, verify complete eradication. Re-scan for surviving agents, scheduled tasks, and modified services that may serve as dormant staging points.
- Build behavioral detection rules: Develop Sigma or EDR rules for: unsigned DLLs loaded by signed binaries, processes making outbound TLS to cloud APIs without a corresponding user session, and unexpected child processes spawned by RMM agents.
Operation ShadowCloud confirms that the boundary between trusted infrastructure and attack infrastructure has effectively dissolved. Detection strategies anchored in reputation and static IOCs are insufficient against adversaries who deliberately compose their toolchains from legitimate components. The defenders who will succeed are those who model behavior—of processes, of identities, and of network flows—rather than merely cataloging bad destinations.