Executive Summary

In early 2026, Kaspersky researchers uncovered Operation ShadowCloud, an active APT intrusion campaign targeting government networks across Asia and Africa. Threat actors abused the legitimate MeshCentral remote-management agent as an initial foothold, then deployed DLL sideloading techniques to load two novel backdoors—GitDoor and GraphDoor—into memory. These implants tunnel command-and-control traffic through trusted cloud platforms including GitHub repositories and the Ably messaging service, effectively blending malicious communications with normal SaaS traffic and evading conventional network-based detection. The modular toolset supports keylogging, credential dumping via Mimikatz, screen capture, file exfiltration, proxy tunneling, and in-memory COFF shellcode execution, enabling deep and persistent access to sensitive government infrastructure.

Operation ShadowCloud represents a maturation of cloud-service-abusing C2 techniques previously observed in campaigns linked to Chinese-speaking threat groups. By routing implant traffic through GitHub APIs and Ably channels, attackers render perimeter-based detection largely ineffective, underscoring the urgent need for egress filtering, multicloud visibility, and zero trust segmentation in government and critical-sector networks.

Why This Matters Now

Nation-state actors are increasingly weaponizing legitimate cloud platforms—GitHub, SharePoint, Ably—as covert C2 channels, making traditional signature-based and perimeter detection obsolete. With attribution indicators pointing to Chinese-speaking APT groups and victims concentrated in government sectors across Asia and Africa, organizations must urgently prioritize cloud egress control, east-west traffic inspection, and zero trust architecture to counter this rapidly evolving threat vector.

Attack Path Analysis

MITRE ATT&CK® Techniques

Potential Compliance Exposure

Sector Implications

Sources

Frequently Asked Questions

GitDoor and GraphDoor route all command-and-control traffic through legitimate cloud services—GitHub APIs and the Ably messaging platform—making malicious communications indistinguishable from normal SaaS traffic. Without cloud-aware egress filtering and deep traffic inspection, perimeter firewalls and signature-based IDS cannot identify or block this activity.

Cloud Native Security Fabric Mitigations and ControlsCNSF

Based on the attack progression modeled above, these are the defensive controls that would constrain each stage.

Aviatrix Zero Trust CNSF is directly relevant to Operation ShadowCloud because the attacker's progression depended entirely on unrestricted lateral movement, unmonitored outbound cloud API traffic, and open egress paths to GitHub and third-party file hosts. By enforcing workload-level segmentation and identity-aware egress controls, CNSF would likely reduce the attacker's reachability across internal segments and constrain the exfiltration channels used to maintain covert persistence.

Initial Compromise

Control: Cloud Native Security Fabric (CNSF)

Mitigation: The attacker's ability to establish an outbound WebSocket tunnel to a hardcoded external IP would likely be constrained by fabric-level visibility and policy enforcement, reducing the reliability of the initial C2 channel and limiting the foothold's ability to stage follow-on payloads.

Privilege Escalation

Control: Zero Trust Segmentation

Mitigation: Zero Trust segmentation would likely limit the attacker's ability to relay coerced NTLM authentication to attacker-controlled destinations by restricting which workloads and network paths can reach external or lateral targets, reducing the effective scope of credential harvesting across the broader environment.

Lateral Movement

Control: East-West Traffic Security

Mitigation: East-west traffic enforcement would likely reduce the attacker's ability to pivot freely across internal network segments via injected SOCKS5 proxies, constraining the reachability of compromised hosts to only explicitly permitted peer workloads and limiting how far laterally the tunneled traffic could propagate.

Command & Control

Control: Multicloud Visibility & Control

Mitigation: Multicloud visibility and control could reduce the attacker's ability to operate undetected by surfacing anomalous outbound HTTPS traffic patterns to cloud API endpoints like api.github.com and rest.ably.io from workloads that have no legitimate business reason to reach those services, potentially constraining covert C2 channel reliability.

Exfiltration

Control: Egress Security & Policy Enforcement

Mitigation: Egress policy enforcement would likely constrain the attacker's ability to exfiltrate data to multiple external destinations — including GitHub, Ably, and upload.gofile.io — by limiting outbound connections from internal workloads to only pre-approved external endpoints, reducing the number of viable exfiltration paths available.

Impact (Mitigations)

Had prior CNSF controls constrained lateral movement and egress paths, the attacker's sustained access would likely have been limited to a smaller subset of workloads, reducing the volume of credentials, keystrokes, and files exposed and narrowing the scope of long-term surveillance achievable across the government network.

Impact at a Glance

Affected Business Functions

  • Government Intelligence and Classified Communications
  • National Security Operations and Diplomatic Networks
  • Public Sector IT Infrastructure and Identity Management
  • Interagency Data Sharing and Internal Government Portals
Operational Disruption

Estimated downtime: N/A

Financial Impact

Estimated loss: N/A

Data Exposure

The campaign specifically targets government sector organizations across Asia and Africa. Data at risk includes sensitive government credentials (usernames, NTLM hashes, cleartext passwords via Mimikatz-based credential dumping), active session tokens, keylogged communications from government officials, screenshots of classified or sensitive workstation activity, full filesystem contents accessible via the file manager module, browser cookies from Edge and Chrome (potentially including authenticated government portal sessions), WhatsApp database decryption keys, and network topology details including ARP tables, active TCP connections, and DNS configurations. The modular shellcode framework also enables persistent lateral movement, service creation, scheduled task manipulation, and NTLM relay attacks via PetitPotam, suggesting prolonged, stealthy access to sovereign government infrastructure with high espionage value.

Recommended Actions

  • •

    Deploy Egress Security & Policy Enforcement with FQDN filtering to block unauthorized outbound connections to attacker-controlled GitHub repositories (api.github.com used with malicious PATs), Ably messaging endpoints (rest.ably.io), and opportunistic exfiltration services (upload.gofile.io) — differentiating sanctioned cloud API usage from covert C2 channels via application-layer policy enforcement rather than IP blocking alone.

  • •

    Implement Multicloud Visibility & Control with deep traffic observability to detect anomalous API call patterns characteristic of GitDoor/GraphDoor C2 — specifically high-frequency GitHub API issue label toggling, repeated PUT/GET operations to atypical repository paths with victim-unique filename patterns, and Ably channel message bursts — establishing behavioral baselines that trigger alerts on deviations consistent with cloud-service-based C2 beaconing.

  • •

    Apply Zero Trust Segmentation with least-privilege identity-based policies to prevent lateral movement enabled by SOCKS5 proxy injection and Erfrp tunneling — enforcing workload-level microsegmentation so that compromised endpoints cannot establish arbitrary east-west connections to other internal hosts, and restricting service-to-service flows to explicitly authorized paths only.

  • •

    Enable East-West Traffic Security inspection on internal network flows to detect and block process injection-facilitated lateral movement (CreateRemoteThread, APC injection, KernelCallbackTable abuse) and proxy tunnel establishment — monitoring for anomalous inter-workload traffic patterns such as unexpected SOCKS5 negotiation, shared memory segment creation for proxy configuration (Local\pc<PID>), and unusual named pipe activity indicative of WinPTY reverse shell deployment.

  • •

    Activate Cloud Native Security Fabric (CNSF) inline enforcement with real-time inspection at cloud network ingress and egress points to intercept encrypted payload delivery disguised as legitimate cloud API traffic — correlating control-plane telemetry with data-plane anomalies such as Base64-encoded AES-encrypted content in GitHub commit messages, XOR-obfuscated filenames following victim-unique-code patterns, and Ably channel subscriptions from enterprise endpoints to external application IDs not associated with sanctioned business workflows.

Secure the Paths Between Cloud Workloads

A cloud-native security fabric that enforces Zero Trust across workload communication—reducing attack paths, compliance risk, and operational complexity.

Cta pattren Image