Unit 42 has identified a sophisticated cyberespionage campaign attributed to the threat actor TGR-STA-0049 (also tracked as REF7707, Earth Alux, and Ink Dragon). Active since at least July 2025, this campaign targets government organizations in Southeast Asia, South America, and Europe. The actor has deployed two previously undocumented Remote Access Trojans (RATs): PerfectPioneer RAT, a Go-based malware, and its more advanced modular successor, KUKURAT. A key feature of this campaign is the use of HTTP/3 for command and control (C2) communications, a novel technique designed to evade detection by blending in with legitimate QUIC protocol traffic. The primary infection vector involves exploiting vulnerable public-facing servers, such as Microsoft Exchange, to install web shells, with phishing serving as a secondary access method. This activity indicates a well-resourced actor focused on long-term intelligence collection and stealth.
The threat actor TGR-STA-0049 has a history of targeting high-value sectors dating back to at least March 2023. Previously, the group was known for deploying Squidoor (also known as FINALDRAFT), an advanced backdoor. This latest campaign, observed since mid-2025, marks a significant evolution in the group's tradecraft with the introduction of PerfectPioneer RAT and KUKURAT. The transition from PerfectPioneer to the modular KUKURAT in March 2026 demonstrates the actor's continuous development and refinement of their toolset.
The campaign's primary objective is cyberespionage, focusing on data collection and exfiltration from strategic government targets. The use of custom malware, advanced evasion techniques like HTTP/3 C2, and a dual-track infection strategy highlights the actor's sophistication and determination to maintain persistent access within compromised networks.
The threat actor employs a multi-stage attack chain characterized by stealth and adaptability.
Server Exploitation (T1190 - Exploit Public-Facing Application): The primary method for initial access is the exploitation of unpatched, internet-facing applications, particularly Microsoft Exchange servers. Upon successful exploitation, the attackers deploy various web shells, including custom variants and publicly known tools like ASPXSpy, Godzilla, Bysunue.aspx, and Suo5. These web shells provide a foothold for executing reconnaissance commands and deploying the primary RAT payloads (T1505.003 - Server Software Component: Web Shell).
Phishing (T1566.001 - Phishing: Spearphishing Attachment): As a secondary vector, the actor uses highly targeted phishing emails. These emails contain decoy PDF documents, such as one impersonating an official document from the Union Election Commission of the Republic of the Union of Myanmar, to trick users into executing the malware.
The campaign's standout feature is its custom malware and C2 infrastructure.
PerfectPioneer RAT: A Go-based RAT first seen in July 2025. It is executed via multiple methods, including direct deployment from a web shell, DLL Side-Loading (T1574.002), and decoy installers.
KUKURAT: Deployed since March 2026, KUKURAT is a modular and more advanced successor to PerfectPioneer, indicating an active development cycle aimed at enhancing stealth and functionality.
HTTP/3 C2 Communication: Both RATs use HTTP/3 over the QUIC protocol for C2. This is a sophisticated choice that offers several advantages for evasion:
T1573.002 - Encrypted Channel: Asymmetric Cryptography).This use of a modern web protocol for C2 (T1071 - Application Layer Protocol) is a clear attempt to bypass traditional network security controls that primarily focus on TCP-based traffic.
The impact of this campaign is primarily strategic, centered on long-term intelligence gathering from sensitive government networks. The compromise of government entities in Southeast Asia and other regions could lead to the theft of classified information, diplomatic communications, and other state secrets. The actor's focus on stealth and persistence means that intrusions could go undetected for extended periods, allowing for continuous data exfiltration.
For affected organizations, the direct impact includes the cost of incident response, forensic analysis, and system remediation. The long-term consequences involve a loss of confidentiality and a potential compromise of national security interests. The actor's ability to rapidly evolve its toolset suggests a persistent and escalating threat to government and potentially other high-value sectors worldwide.
No specific Indicators of Compromise (IOCs) such as IP addresses, domains, or file hashes were provided in the source report.
Security teams may want to hunt for the following patterns to detect related activity:
w3wp.exe or httpd.execmd.exe, powershell.exe, or unknown binaries.*.aspx.aspx files in web-accessible directories on Exchange and IIS servers.Bysunue.aspx, Suo5whoami, ipconfig, net userDetecting this threat requires a multi-layered approach focusing on network anomalies and endpoint behaviors.
Network Traffic Analysis: Implement Network Traffic Analysis (D3-NTA) to monitor egress traffic on UDP port 443. Establish a baseline for legitimate QUIC traffic from browsers and cloud services. Use tools with JA3/JA3S and JARM-like fingerprinting capabilities for QUIC (e.g., QUIC-fingerprinting) to identify anomalous clients that do not match standard browsers.
Endpoint Detection and Response (EDR): Deploy EDR solutions to monitor for suspicious process chains. Create rules to detect web server processes (e.g., w3wp.exe) spawning command-line interpreters or making outbound network connections to unusual destinations. This is a key part of Process Analysis (D3-PA).
Log Analysis: Ingest and analyze web server logs, Windows Event Logs (especially process creation 4688), and firewall logs. Look for unusual requests to .aspx pages, access from anomalous IP addresses, and unexpected UDP 443 connections from servers.
Threat Hunting: Proactively hunt for web shells using file integrity monitoring and scanners. Hunt for evidence of DLL side-loading by monitoring for legitimate, signed executables loading unsigned or abnormally named DLLs from unusual directories.
Defending against TGR-STA-0049 requires both immediate tactical actions and long-term strategic improvements.
Patch Management (M1051 - Update Software): The most critical mitigation is to apply security patches to all internet-facing systems, especially Microsoft Exchange, web servers, and VPNs. Prioritize vulnerabilities known to be exploited in the wild.
Network Segmentation (M1030 - Network Segmentation): Isolate critical servers from each other and from the broader user network. Restrict communication from web servers to internal systems to prevent lateral movement after a breach.
Egress Traffic Filtering (M1037 - Filter Network Traffic): Deny all outbound traffic by default and only allow what is necessary. Specifically, restrict or heavily monitor outbound UDP 443 traffic from servers that have no business initiating QUIC connections.
Application Control (M1038 - Execution Prevention): Use application allowlisting on critical servers to prevent the execution of unauthorized executables, including Go-based binaries dropped by the attacker. This can prevent the RATs from running even if the initial exploit is successful.
User Training and Awareness (M1017 - User Training): To counter the phishing vector, conduct regular security awareness training to help users identify and report suspicious emails and attachments.
Regularly patch public-facing applications like Microsoft Exchange to prevent initial access via exploitation.
Mapped D3FEND Techniques:
Implement egress filtering to block or monitor unusual outbound traffic, such as QUIC (UDP/443) from servers.
Mapped D3FEND Techniques:
Use application control to prevent unauthorized executables, like the Go-based RATs, from running on servers.
Segment networks to contain breaches and prevent lateral movement from a compromised web server to the internal network.
Train users to identify and report phishing attempts to mitigate the secondary infection vector.
Utilize endpoint protection platforms to detect and block known web shells and RAT payloads.
Mapped D3FEND Techniques:
Given that the primary infection vector for TGR-STA-0049 is exploiting vulnerable public-facing servers like Microsoft Exchange, implementing a robust and timely software update process is the most effective defense. Organizations must prioritize patching for all internet-facing systems. This involves not only applying vendor-supplied patches as soon as they are released but also having an asset inventory to ensure all such systems are known and tracked. A risk-based approach should be adopted, where vulnerabilities known to be actively exploited by threat actors like TGR-STA-0049 are patched immediately, even if it requires emergency change control procedures. For systems that cannot be patched immediately, virtual patching via a Web Application Firewall (WAF) or Intrusion Prevention System (IPS) should be deployed as a compensating control to block exploit attempts against known vulnerabilities.
To counter the actor's use of HTTP/3 for C2, network traffic analysis is critical. Since HTTP/3 runs over UDP/443, traditional TCP-focused monitoring will miss it. Security teams should deploy network sensors and flow analysis tools capable of parsing and fingerprinting QUIC traffic. The first step is to establish a baseline of legitimate QUIC traffic within the environment, identifying known clients (browsers, mobile apps) and servers (Google, Cloudflare). With a baseline, create alerts for any QUIC traffic originating from servers that should not be acting as clients (e.g., Exchange servers, database servers). Additionally, use QUIC fingerprinting techniques to identify non-standard or suspicious client implementations that do not match common browsers. This allows for the detection of the custom C2 channels used by PerfectPioneer and KUKURAT, even though the traffic is encrypted.
To detect the post-exploitation phase where the actor uses web shells, process analysis on web servers is essential. Configure EDR tools or use native logging (like Windows Event ID 4688 with command-line logging enabled) to monitor process parent-child relationships. A web server worker process (e.g., w3wp.exe for IIS, httpd.exe for Apache) should almost never spawn command-line shells (cmd.exe, powershell.exe) or reconnaissance tools (whoami.exe, ipconfig.exe). Create high-severity alerts for this specific behavior. This technique is highly effective at detecting web shell activity, regardless of the web shell's code or obfuscation, as the malicious commands must eventually be executed on the underlying operating system. This provides a reliable detection point in the attack chain before the actor can deploy the primary RAT payload.
On critical servers like Microsoft Exchange, which have a predictable set of required applications, executable allowlisting can prevent the execution of the PerfectPioneer and KUKURAT RATs. By creating a policy that only allows known, legitimate executables to run, any unauthorized binary dropped by the attacker will be blocked. This is particularly effective against custom malware that may not have a known signature for traditional antivirus. Implementing allowlisting in 'enforce' mode can be challenging, so organizations can start in 'audit' mode to build a baseline of normal activity. This defense hardens the server against unauthorized code execution, effectively neutralizing the attacker's payload even if they successfully exploit a vulnerability and upload the malware.
TGR-STA-0049 activity is first observed, initially using tools like the Squidoor backdoor.
The cyberespionage campaign detailed in the report begins, with the first sighting of the custom Go-based PerfectPioneer RAT.
The threat actor deploys KUKURAT, a more advanced modular RAT, and begins transitioning its infrastructure away from PerfectPioneer.

Cybersecurity professional with over 10 years of specialized experience in security operations, threat intelligence, incident response, and security automation. Expertise spans SOAR/XSOAR orchestration, threat intelligence platforms, SIEM/UEBA analytics, and building cyber fusion centers. Background includes technical enablement, solution architecture for enterprise and government clients, and implementing security automation workflows across IR, TIP, and SOC use cases.
CyberNetSec.io uses automation to assist source monitoring, deduplication, observable extraction, and structured intelligence generation. Published analysis follows human-defined editorial standards and adds defensive context including MITRE ATT&CK, D3FEND, STIX, and Sigma where applicable. Read our editorial policy.
Help others stay informed about cybersecurity threats
Every tactic, technique, and sub-technique used in this threat has been identified and mapped to the MITRE ATT&CK framework for consistent, actionable threat language.
Observables and indicators of compromise (IOCs) have been extracted and cataloged. Risk has been assessed and correlated with known threat actors and historical campaigns.
Detection rules, incident response steps, and D3FEND-aligned mitigation strategies are included so your team can act on this intelligence immediately.
Structured threat data is packaged as a STIX 2.1 bundle and can be visualized as an interactive graph — relationships between actors, malware, techniques, and indicators.
Sigma detection rules are derived from the threat techniques in this article and can be converted for deployment across any major SIEM or EDR platform.