ETCISO reports China-linked Operation Dragon Weave abusing Azure storage
ETCISO reports a China-linked campaign, Operation Dragon Weave, using Azure Blob Storage for C2; treat unexpected .pdf.lnk archives with caution.
- Published
- Ecosystem
- CloudDesktops, browsers and mobile
- Exploitation
- Yes, according to ETCISO, which describes a targeted campaign seen in the wild; no independent verification and no victim confirmation in the sources
What happened
According to ETCISO, researchers (not named in the article) identified a targeted cyber-espionage campaign called Operation Dragon Weave and assessed with moderate confidence that it is linked to a China-based threat actor. ETCISO says the campaign targets officials and citizens in the Czech Republic and Taiwan. This is a single-outlet report, and the attribution is the researchers’ assessment as relayed by ETCISO, not an established fact. The article does not say who the victims are, how many there were, or whether any intrusion was confirmed by an affected organisation.
ETCISO reports the following details:
- Discovery: Researchers say they found the campaign after a suspicious ZIP archive was submitted from Taiwan “earlier this year”. The exact date is not confirmed. The archive reportedly held files posing as a Traditional Chinese “Project Application Review Result Notification”. A Czech-language decoy appointment notice impersonating the Czech Social Security Administration was reportedly part of the same operation.
- Two infection paths: In one, a Windows shortcut disguised as a PDF launches a hidden VBScript and PowerShell sequence that decrypts a payload container. In the other, a Rust-based executable dropper deploys a decoy PDF, encrypted configuration material and a malicious DLL. Both reportedly converge on a DLL sideloading stage.
- Loader: Researchers named the Rust-based loader RUSTCLOAK. ETCISO says it checks the machine name against a list of more than 100 sandbox and researcher-system identifiers, decrypts its payload through a three-layer routine, and runs it in memory using Windows fibers.
- Payload: The final payload, AZUREVEIL, is described as a 64-bit Adaptix command-and-control agent. ETCISO lists remote command execution, file operations, data exfiltration, process discovery, network enumeration, proxying and in-memory execution of Beacon Object Files, with 36 post-exploitation commands identified.
- Azure abuse: According to ETCISO, AZUREVEIL uses Microsoft Azure Blob Storage as a dead-drop command-and-control channel. The infected device uploads an encrypted beacon, operators place commands in the storage account, and the malware retrieves them and returns results as encrypted blobs. Researchers also reportedly found a hardcoded Shared Access Signature token in the malware configuration, valid for a full year, with read, write, delete and upload permissions on the container.
Not confirmed in the source: the researchers’ or vendor’s name, any statement from Microsoft, whether the storage account was taken down, indicators of compromise, and the number of affected targets.
Am I affected?
The sources describe targeting of officials and citizens in the Czech Republic and Taiwan. ETCISO also advises government bodies, research organisations, financial institutions and technology companies to be cautious. Whether other regions or sectors are targeted is not confirmed.
You may have relevant exposure if your users could receive unexpected ZIP archives, shortcut files presented as PDFs, or executables presented as documents. No CVE is cited in the source, and no vendor patch is relevant to this campaign as reported.
What to do now
The source’s own recommendations are short, and the steps below stay within them:
- Warn users, especially in government, research, finance and technology roles, to be cautious with unexpected archives and files with double extensions such as .pdf.lnk, or executables presented as documents.
- Monitor for unusual PowerShell and VBScript activity.
- Investigate DLL sideloading behaviour.
- Inspect unexpected use of cloud-storage services, including HTTPS traffic to Azure storage from endpoints that have no business reason to use it.
- Check that your security controls can detect encrypted or fileless execution chains, since the reported loader runs its payload in memory.
No indicators of compromise were published in the ETCISO article, so there is nothing further to hunt for from this source alone.