What researchers found
A legitimate agent opened the door to new implants
Kaspersky reports an active campaign against government networks in Asia and Africa. The intruders abused MeshAgent, a legitimate remote-management utility, to deploy two backdoors the researchers call GitDoor and GraphDoor. The implants used GitHub, Microsoft SharePoint and Ably for command traffic and plug-in delivery. Kaspersky says the way the attackers first installed MeshAgent is still unclear.
GitDoor used GitHub repositories and issues to move commands and results. GraphDoor supported additional plug-ins, including keylogging, process listing and screen capture. This matters because the network destinations can look like everyday cloud use while endpoint behavior tells a very different story.
Attribution is still a research lead
Defender workflow
Join the host trail to the cloud trail
- 1
Trace remote-management changes. Look for newly installed or unexpectedly reconfigured MeshAgent instances on sensitive systems. Compare deployment time with approved administration records.
- 2
Inspect the host sequence. Use the researcher-provided indicators to hunt for side-loaded components, staging paths, unusual child processes and plug-in activity. Preserve the sequence rather than treating one file hash as the entire case.
- 3
Correlate outbound calls. Investigate unusual GitHub API, SharePoint and Ably use from those same hosts, including account, repository and timing context. Do not block an entire service based only on its hostname.
Defender note
Normal traffic needs abnormal context
A cloud destination becomes more useful when joined to the device that called it, the process that made the request and the account that authenticated. Kaspersky's two reports include detailed indicators; use them as starting points, then validate against your own software inventory and logs.