KUKURAT: HTTP/3 implants in Southeast Asian government networks, deployed by logon script
Unit 42 has documented two new remote access tools used against Southeast Asian governments by a cluster four vendors track under four names. The transport is new. The persistence and the mail access rely on administrative features most estates already run.
A new transport on an old intrusion set
Palo Alto Networks Unit 42 has published research on two remote access tools used against government entities in Southeast Asia [1]. One, PerfectPioneer, is written in Go and has been seen since at least July 2025. The other, KUKURAT, is a modular C++ successor first observed in March 2026, deployed into networks PerfectPioneer had already reached [1].
Both carry command and control over HTTP/3, which runs on QUIC over UDP [1][10]. That is the headline. The operational lesson is elsewhere. The implants were spread by domain logon scripts and paired with bulk mailbox permissions. Those are standard administrative features, and both can be audited today.
One cluster, four names
Unit 42 tracks the activity as TGR-STA-0049 and lists REF7707, Earth Alux and Ink Dragon as other names for it [1]. Its own February 2025 report called the cluster CL-STA-0049, assessed with moderate-high confidence that the activity originates in China, and dated it to at least March 2023 [2]. Check Point equates Ink Dragon with Earth Alux, Jewelbug, REF7707 and CL-STA-0049 [5].
Each vendor has seen a different slice.
- Elastic found the cluster in a South American foreign ministry and saw possible victims among eight Southeast Asian telecommunications and internet infrastructure companies [3].
- Trend Micro dated Earth Alux to the second quarter of 2023 and listed Thailand, the Philippines, Malaysia and Taiwan in Asia-Pacific, and Brazil in Latin America, among its targets [4].
- Unit 42’s earlier work found government, defence, telecommunications, education and aviation targets in Southeast Asia and South America [2]. Singapore’s IMDA issued an advisory on that report [6].
- Check Point found the group turning compromised IIS servers into relay nodes for other victims’ traffic, and targeting governments in Europe, Southeast Asia, South America and Africa [5].
The names are not interchangeable labels for identical observations. They are overlapping views of one long-running set of operations.
What Unit 42 found
Initial access was mostly through unpatched Microsoft Exchange and other web servers, followed by web shells [1]. Unit 42 names no specific CVE [1]. A secondary route used decoy PDFs and government-themed lookalike domains. One decoy impersonated a 2025 notice from Myanmar’s Union Election Commission [1].
PerfectPioneer exists in six variants. Some carry a command filter Unit 42 describes as a safety switch: 41 blocked keywords, 16 blocked execution patterns and 12 protected operating system paths [1]. In Unit 42’s reading, it “prevents the operators from making mistakes that could result in the activity being detected” [1].
KUKURAT holds no post-exploitation code in its core binary. Unit 42 identified at least 12 modules loaded into memory from the command server, covering lateral movement, credential brute-forcing, tunnelling and privilege elevation [1]. It can generate decoy activity: ten requests per cycle to popular websites, and routine-looking registry and temporary-file writes [1]. A watchdog relaunches it within 15 seconds of losing a heartbeat. In one deployment it sat in a folder named after a security product’s own directory [1].
Credentials came from LSASS memory, registry hive dumps and DCSync [1]. The LSASS dump called the Windows comsvcs.dll MiniDump export by ordinal rather than by name, which defeats detections that look for the function name [1]. Judged from filenames, collection targeted documents on international relations and domestic politics [1].
The two features that did the work
The first is the network logon script. After compromising domain controllers, the operators installed malicious logon scripts so that users authenticating to the domain received KUKURAT [1]. MITRE tracks this as T1037.003 [7]. A single script can reach many or all systems in a domain, and MITRE’s listed mitigation is to restrict write access to logon scripts to specific administrators [7].
The second is Exchange mailbox permission. The operators checked which accounts held the ApplicationImpersonation role, then looped over every mailbox granting a compromised account FullAccess with AutoMapping disabled [1]. FullAccess exposes every item, including calendar entries marked private [9]. AutoMapping off means the mailbox is not added to that account’s Outlook profile [9]. The grant is complete and invisible to the user.
Microsoft finished removing ApplicationImpersonation from Exchange Online in March 2025 [8]. Its notice covers Exchange Online only [8]. The intrusions began on exploited Exchange servers [1], so on-premises estates should check that role directly.
Why HTTP/3 matters, and where it fails
Unit 42 notes that HTTP/3 may bypass inspection built around TCP, and that UDP traffic cannot be passively intercepted as TLS sessions often are [1]. PerfectPioneer falls back to HTTP/2 when HTTP/3 fails [1]. That fallback is standard behaviour. RFC 9114 says that when blocked UDP prevents a QUIC connection, clients should try TCP-based HTTP [10].
So blocking outbound UDP 443 from servers and administrative hosts does not stop the implant from talking. It pushes the traffic back onto channels existing inspection already covers. Unit 42 recommends exactly that, or logging and inspecting QUIC [1].
What to do
- Inventory who can write to SYSVOL and NETLOGON and to Group Policy logon-script settings. Alert on changes and on unusual processes started under user SIDs at logon [1][7].
- Enumerate Exchange mailbox permissions. Look for one account holding FullAccess across many mailboxes, and for grants made with AutoMapping disabled [1][9].
- On Exchange Server, review ApplicationImpersonation assignments and remove any without a documented owner [1][8].
- Block or inspect outbound QUIC from servers, domain controllers and administrative workstations [1][10].
- Detect rundll32 loading comsvcs.dll, including ordinal-based calls, and watch for DCSync from hosts that are not domain controllers [1].
- Patch internet-facing Exchange and web servers and hunt for web shells in their directories, as IMDA advised for the earlier Squidoor activity [1][6].
- Check Unit 42’s published indicators against DNS and proxy logs [1].
For Southeast Asian ministries, this cluster has been present since at least 2023 under several names [2][4]. The transport will change again. Logon scripts and mailbox permissions are under the defender’s control now, and they are where this campaign was most visible.
Sources
Every R3KONX article cites its primary material. 10 sources, in order of first citation. Links open the original publication.
- QUIC and covert: novel HTTP/3-powered RATs target Southeast Asian governments Palo Alto Networks Unit 42 · 2026-11-16
- Squidoor: suspected Chinese threat actor's backdoor targets global organizations Palo Alto Networks Unit 42 · 2025-02-27
- From South America to Southeast Asia: the fragile web of REF7707 Elastic Security Labs · 2025-02-13
- The espionage toolkit of Earth Alux Trend Micro Research · 2025-03-31
- Ink Dragon's relay network and offensive operation Check Point Research · 2025-12-16
- Squidoor backdoor targets various organisations for espionage Infocomm Media Development Authority (IMDA), Singapore · 2025-02-27
- Boot or Logon Initialization Scripts: Network Logon Script (T1037.003) MITRE ATT&CK · 2025-10-24
- Critical update: ApplicationImpersonation RBAC role deprecation in Exchange Online Microsoft Exchange Team Blog · 2025-03-13
- Add-MailboxPermission Microsoft Learn · accessed 2026-11-18
- RFC 9114: HTTP/3 IETF / RFC Editor · 2022-06
Researched and written by the R3KONX Analysis Desk from the cited primary material. The technical findings on PerfectPioneer and KUKURAT come from a single research team, Palo Alto Networks Unit 42; earlier reports from Elastic, Trend Micro and Check Point are cited for the cluster's history. Victim countries and agencies are not named by Unit 42 and are not named here. Attribution is reported as each researcher's assessment. Corrections: event@r3konx.asia.
