Skip to main content
Emerging ThreatsMalware & Ransomware

GraphDoor Backdoor Exposes Cloud-Based Espionage Operation

Modern office building with cloud workspace hint and sleek laptop in foreground.

The malware first opens a TLS connection to login.microsoftonline.com on port 443.

GraphDoor's Microsoft Graph–based command-and-control

GraphDoor establishes C2 by authenticating a malicious application — not a user — against login.microsoftonline.com using a client credentials flow. The backdoor decrypts three embedded AES strings (UUID path segment, client_id, client_secret), generates an X‑CSRF‑TOKEN and a preset User‑Agent, and POSTs to the tenant token endpoint. If it receives an access token, the implant puts encrypted victim data into SharePoint via Microsoft Graph by creating a file named main.%victim_unique_code%.js.map in a specified drive on buildersemp.sharepoint[.]com. The PUT body includes the Base64‑encoded, AES‑encrypted victim information under the JSON key "content" with a message value "commit from INSOMNIA".

Plug‑ins: screenshots, keylogger, process listing, proxy channels and more

After initial exfiltration, GraphDoor pulls plug‑ins from SharePoint: scr.ts (screenshot capture), pr.ts (process listing), and kl.ts (keylogger). Plug‑ins are fetched in parallel via Microsoft Graph list queries filtered by Title (for example, startswith(fields/Title,'scr.ts')). The keylogger writes encrypted keystrokes to %APPDATA%\\Microsoft\\SystemCertificates\\Cache\\logs.dat using a random 32‑byte XOR key masked by a hard‑coded 32‑byte key; it installs low‑level keyboard and mouse hooks and signals start/stop via a named object called keylogger###Global\\OneDriveStandaloneUpdater{{%X-%X}}.

The process‑listing plug‑in acquires SeDebugPrivilege, enumerates processes, formats each line as bof-process##################

Additional plug‑ins include moveDir.ts (moves legitimate executable, loader DLLs and encrypted payload config.ini to a target path and can trigger self‑termination and file deletion) and a suite of proxy plug‑ins: channel.ts (Erfrp‑derived Go reverse proxy; injected reflectively, reads config from Local\\pc%PID%), abchannel.ts (an Ably client using the official Go SDK; reads a JSON Token and channel name from Local\\pcs%PID% and subscribes to json and json.send events), and ab2channel.ts (a covert SOCKS5 proxy tunneling TCP over Ably’s Pusher‑compatible WebSocket endpoint, using private channels derived from instance_id).

Loader and execution techniques

GraphDoor uses layered stealth: it resolves Windows APIs at runtime by hashing DLL/function names with DJB2, invokes functions via a vectored exception handler that executes miniature routines when an exception is raised, and stores per‑run data under C:\\ProgramData\\Intel_Log\\<random‑GUID>. Plug‑ins themselves combine a small loader stub with a COFF object marker sequence (0x1C 0x3F 0xE6 0xE9). The stub allocates executable memory, relocates sections and calls a go entry function inside the COFF payload. The backdoor supports advanced in‑memory loading variants: a shell command for cmd.exe /C, and an adsmload routine that decodes payloads formatted as ASCII MAC addresses, Base64‑decodes, converts via RtlEthernetStringToAddressA, and injects MZ executables or shellcode into memory. Shared memory segments such as Local\\sm<PID> and Local\\pc<PID> are used to pass configurations to injected components.

Infrastructure, overlapping tooling and observed staging

The operation avoids embedded hard‑coded C2 domains by retrieving hostnames and ports through the proxy and Ably channels. Analysts observed proxy servers and a list of IP addresses used as C2 and proxy endpoints (for example 104.194.154.28, 103.106.230.33, 123.58.205.105 among many others), and two domains—twnic[.]top and ekmt[.]tw—resolving to 103.106.230.33 and 123.58.205.105 respectively; those domains were also tied to Cobalt Strike beacon servers on systems infected with GraphDoor. The report lists multiple proxy server entries with ASNs (for example AS 14956 RouterHosting LLC; AS 53724 EXTRAVM LLC; AS 136258 BrainStorm Network, Inc) and specific proxy credentials observed in infrastructure logs.

Overlap with Chinese‑speaking activity was noted: GitDoor and GraphDoor implants appeared in staging directories near deployments tied to groups labeled in the report as FamousSparrow and CopperTurtle. Examples include a FamousSparrow staging directory %ProgramData%\\excint\\ (excint.exe, wtsapi32.dll) with malicious wtsapi32.dll (MD5 733f8002aa9531b25384c0014d15cc1f) and RC4 key iotrh^%4CFGTj; and CopperTurtle activity involving pdfset.exe (MD5 45b3aa39bc33528650d9181cd946b2df) that injected PLEAD RAT. Dates provided in the report include staging artifacts created 2026.03.05–06 and 2026.05.03–04.

What this means for technologists, enterprises, and cloud administrators

  • Technologists and security teams: watch for unusual Microsoft Graph application registrations and client‑credentials flows, unexpected PUTs creating main.*.js.map files in SharePoint document libraries, and the presence of named pipes and shared‑memory segments such as Local\\pc<PID> and Local\\sm<PID> used by injected binaries.
  • Enterprises and procurement/IT leaders: the report flags the introduction of legitimate remote‑management tools (for example MeshCentral Agent) as a suspicious event when seen alongside these indicators; the moveDir behavior shows how an attacker can relocate legitimate binaries and backdoors together.
  • Cloud administrators for SharePoint and Ably: monitor application‑level tokens, unusual client IDs and file creations (main.%victim_code%.js.map), and anomalous subscriptions or private channels that match the Ably patterns described (for example private-socks5--request/response).

GraphDoor and its plug‑in suite demonstrate a deliberate decision to use trusted cloud APIs as stealthy transport — authentication with login.microsoftonline.com, file stores on buildersemp.sharepoint[.]com, and messaging via Ably are central to the operation. The report leaves open how actors initially introduced legitimate management agents into victim environments, and documents infrastructure and staging artifacts that investigators can map into detection and response playbooks.

Original report: https://securelist.com/operation-shadowcloud-graphdoor/122005/