Cambodia-Focused Threat Cluster Uses Localized Phishing and Multi-Stage Malware
Detection stack
- AIDR
- Alert
- ETL
- Query
Summary
An unattributed threat cluster is targeting organizations in Cambodia with localized phishing lures. The attack relies on a complex multi-stage infection chain involving DLL sideloading, shellcode extraction from PNG files, and process injection. The campaign also abuses a Bring Your Own Vulnerable Driver (BYOVD) technique to disable security software.
Investigation
The Acronis Threat Research Unit identified the campaign while analyzing compressed archives containing Cambodia-themed lures. Researchers traced the infection from an Inno Setup installer to the deployment of SparkRAT. The malware was also observed performing token manipulation, AMSI/ETW patching, and abusing the vulnerable arsdrv.sys driver to terminate security processes.
Mitigation
Organizations should deploy robust endpoint protection and monitor for suspicious driver installations, with particular attention to BYOVD activity. Patching vulnerabilities such as CVE-2026-36425 and limiting administrative privileges can reduce the impact of token manipulation. Monitoring unauthorized service creation and scheduled task activity can also help identify persistence.
Response
If malicious activity is detected, affected hosts should be isolated immediately to prevent further lateral movement or C2 communication. Investigators should examine the C:\Drivers directory and inspect processes such as vssvc.exe, ctfmon.exe, and svchost.exe for injected code. Windows Event Logs should also be reviewed for suspicious sc.exe service creation and schtasks.exe modifications.
Attack Flow
We are still updating this part.
Detections
Suspicious Command and Control by Unusual Top Level Domain (TLD) DNS Request (via dns)
Possible Manual Service or Driver Install for Persistence (via cmdline)
Possible Schtasks or AT Usage for Persistence (via cmdline)
IOCs (HashSha256) to detect: Cambodia-focused cluster uses multistage infection chain with localized lures Part 2
IOCs (HashSha256) to detect: Cambodia-focused cluster uses multistage infection chain with localized lures Part 1
IOCs (HashMd5) to detect: Cambodia-focused cluster uses multistage infection chain with localized lures
Malicious DLL Sideloading and Process Injection in Cambodia-Focused Campaign [Windows Sysmon]
Detect Communication with Unattributed C2 Servers in Cambodia-focused Campaign [Windows Network Connection]
Suspicious Multi-Stage Infection Chain with Token Impersonation and Reflective PE Loading [Windows Process Creation]
Simulation Execution
Prerequisite: The Telemetry & Baseline Pre-flight Check must have passed.
Rationale: This section details the precise execution of the adversary technique (TTP) designed to trigger the detection rule. The commands and narrative MUST directly reflect the TTPs identified and aim to generate the exact telemetry expected by the detection logic. Abstract or unrelated examples will lead to misdiagnosis.
-
Attack Narrative & Commands: An adversary has successfully established a foothold on a Windows workstation via a localized lure. Having performed credential dumping (T1055) to escalate privileges, the malware now attempts to establish an encrypted Command and Control (C2) channel. To avoid detection, the malware targets the specific infrastructure identified in the Cambodia-focused campaign:
nuihuw.top. The simulation will use a PowerShell command to initiate a connection to this domain on port 443, mimicking the malware’s callback. -
Regression Test Script:
# Simulation script to trigger detection of C2 communication # This mimics a malware callback to the identified malicious domain $C2Domain = "nuihuw.top" $C2Port = 443 Write-Host "[+] Initiating simulated C2 communication to $C2Domain on port $C2Port..." -ForegroundColor Cyan try { # Using Invoke-WebRequest to generate an HTTPS connection to the malicious domain # Note: In a real environment, this would likely fail due to lack of actual C2, # but the connection attempt/DNS lookup will generate the required network telemetry. Invoke-WebRequest -Uri "https://$C2Domain" -Method Get -TimeoutSec 5 } catch { Write-Host "[!] Connection failed (as expected if domain is sinkholed), but telemetry should be generated." -ForegroundColor Yellow } Write-Host "[+] Simulation complete." -ForegroundColor Green -
Cleanup Commands:
# No persistent changes made by this simulation; # Ensure any local temporary files or logs generated are cleared. Write-Host "[+] Cleaning up simulation environment..." -ForegroundColor Cyan