ServicesBlogPricingContactContact Now
Cyber Security5 min read

Operation ShadowCloud: GitDoor and GraphDoor C2 Backdoors

Operation ShadowCloud: GitDoor and GraphDoor C2 Backdoors

Introduction

Kaspersky has disclosed an active intrusion campaign aimed at government organizations in Asia and Africa, and the tooling at its center is notable less for what it does than for where it hides. The Russian security vendor, which codenamed the activity Operation ShadowCloud, says the campaign delivers two previously undocumented backdoors — GitDoor and GraphDoor — that route command-and-control (C2) traffic through legitimate cloud services, specifically GitHub and Microsoft SharePoint.

Kaspersky said it identified the campaign in early 2026. The finding follows a pattern that has become increasingly common over the past few years but is sharper here in its execution: rather than standing up attacker-owned infrastructure that defenders can block by domain or IP reputation, the operators appear to be borrowing platforms that most enterprises already trust, already allow through their egress controls, and in many cases already pay for.

For security teams, the practical takeaway is uncomfortable. A detection strategy built primarily on blocking known-bad infrastructure has very little to say about malware that talks to github.com or to a tenant's own SharePoint environment.

What is actually known about Operation ShadowCloud

The public picture so far is narrow, and it is worth being precise about the boundaries of what has been confirmed versus what remains undisclosed.

  • Targeting: government sectors in Asia and Africa are the identified victims of the campaign.
  • Tooling: two backdoors, named GitDoor and GraphDoor, both described as previously undocumented.
  • C2 transport: the backdoors abuse legitimate services — Microsoft SharePoint and GitHub — as covert command-and-control channels.
  • Attribution of discovery: Kaspersky, the Russian cybersecurity company, identified the campaign in early 2026 and assigned it the codename Operation ShadowCloud.

The naming strongly suggests a split of duties, with GitDoor oriented toward GitHub and GraphDoor toward SharePoint, but the detailed technical breakdown of each implant is not yet public in the material available. Also not yet public: the initial access vector, the number of confirmed victims, the identity or sponsorship of the operators, whether the backdoors are bespoke or shared across multiple threat groups, and any indicators of compromise that defenders could hunt against today. Until those details surface, organizations should treat the campaign as an active, unresolved threat rather than a historical case study.

Why trusted cloud services make effective cover

The appeal of this approach for an intrusion operator is straightforward. Enterprise networks are typically configured to permit outbound traffic to major developer platforms and productivity suites, because blocking them would break engineering workflows and business operations. That permission is granted at the network layer, often without full inspection of the content inside the session.

GitHub and SharePoint both offer legitimate, high-volume API surfaces that generate a constant stream of encrypted requests from ordinary business activity. A backdoor that blends into that noise is difficult to isolate through domain reputation alone, and it does not require the attacker to register new infrastructure that might be flagged by threat intelligence feeds. Traffic to a widely used SaaS platform also tends to survive firewall changes, proxy migrations and geo-blocking policies that would otherwise interrupt an attacker-owned C2 server.

There is a second-order problem as well. When the C2 channel is a service the organization itself uses, the evidence of malicious activity may sit inside that service's own audit logs — logs that security teams frequently do not ingest into their SIEM, or ingest at a volume too low to alert on. The attacker effectively gains a control channel and a place to store data that sits outside the perimeter the defenders are watching most closely.

Practical mitigation: what defenders should do now

Because the campaign's defining characteristic is abuse of legitimate services, mitigations need to shift weight from blocking to observing. Concrete steps worth prioritizing:

  • Instrument the platforms themselves. Pull GitHub audit log events and SharePoint unified audit logs into central detection. Alert on new personal access tokens, new OAuth applications, unusual repository or site access patterns, and activity from unexpected geographies or user agents.
  • Inspect egress, do not just allow it. Where TLS inspection is feasible, apply it to traffic destined for developer and productivity platforms. Where it is not, use proxy-level metadata — request volume, timing regularity, endpoint paths, user agent strings — to identify beaconing behaviour.
  • Baseline normal API usage. Establish what volume and cadence of GitHub and SharePoint API calls is normal for each business unit, then treat sustained low-and-slow polling from a workstation or server as an anomaly worth investigating.
  • Constrain credentials and tokens. Enforce least privilege on service accounts and personal access tokens, shorten token lifetimes, and review third-party OAuth grants to Microsoft and GitHub on a scheduled basis.
  • Hunt for the implants by behaviour. Look for processes on government-facing systems that make periodic outbound connections to these platforms without a corresponding user session, and for persistence mechanisms that do not match approved software deployment.
  • Prepare an incident response playbook for SaaS-based C2. Deciding in advance who can revoke tokens, disable an OAuth app and preserve platform logs will save critical hours if the campaign reaches your estate.

Grivyonx Expert Analysis

Operation ShadowCloud is a reminder that the perimeter has not disappeared — it has been rented from third parties. GitDoor and GraphDoor matter less as individual malware families than as evidence that adversaries now treat mainstream SaaS platforms as free, resilient and pre-approved C2 infrastructure. The defensive gap this exposes is largely organizational rather than technical: network teams own egress policy, identity teams own OAuth grants, and platform owners hold the audit logs, yet few organizations correlate all three in a single detection pipeline. Until they do, an implant that never contacts a suspicious domain will keep slipping past controls tuned for a threat model that no longer matches reality. The absence of published indicators for this campaign makes behavioural detection the only viable near-term posture.

Conclusion

Kaspersky's disclosure of Operation ShadowCloud adds two names — GitDoor and GraphDoor — to a growing list of backdoors that treat trusted cloud services as transport rather than target. Government networks in Asia and Africa are the confirmed focus so far, but the technique is platform-agnostic and portable, and there is no technical reason it would stay confined to those regions or that sector. The most useful response is not a new blocklist entry but a harder look at what is already allowed out of your network, and at whether you would be able to see abuse of it if it happened tomorrow. Teams building that visibility into their pipelines — and automating the triage of the resulting alerts — can lean on Grivyonx's AI automation, DevSecOps and cloud security services to shorten the distance between a suspicious API call and a confirmed incident.

  • #Operation ShadowCloud
  • #GitDoor
  • #GraphDoor
  • #Kaspersky
  • #GitHub C2
  • #SharePoint security
  • #backdoor malware
  • #cyber espionage
Gourav Rajput

Gourav Rajput

Founder of Grivyonx Technologies

Cyber Security

Lazarus Group Operation FlashHole Targets South Korean Firms

North Korea's Lazarus Group has launched Operation FlashHole, targeting South Korean organizations in construction, software, and wire-communication manufacturing. The campaign abuses legitimate security software and employs post-quantum encryption to evade detection.

Cyber Security

Bronze Sandcastle APT Exploits Sandboxie DLL Sideloading in New Campaign

Security researchers at Sophos have identified a previously undocumented China-aligned threat cluster dubbed Bronze Sandcastle, active since mid-2025 across organizations in Asia and Africa. The group's signature technique involves abusing Sandboxie's legitimate isolation software to sideload malicious DLLs, enabling stealthy backdoor deployment on compromised systems. This campaign represents a significant evolution in DLL sideloading tactics, leveraging a trusted sandboxing application rather than the more commonly exploited system binaries. The discovery highlights how threat actors continue to innovate by weaponizing legitimate security tools to evade detection.

Cyber Security

Iranian Cavern C2 Framework Evolves with DNS & Google Apps Script Stealth

Iranian state-sponsored actors continue refining the Cavern command-and-control framework, now leveraging DNS tunneling and Google Apps Script to mask malicious traffic as legitimate cloud activity. Kaspersky researchers have uncovered previously undocumented components that significantly expand the framework's stealth capabilities against Israeli targets. This evolution demonstrates a calculated shift toward living-off-the-land techniques that abuse trusted infrastructure, making detection substantially harder for conventional security controls.