← All hunts high TLP:CLEAR Part 1 of 2

TGR-STA-0049 Initial Access via Exploitation and Phishing

An intruder has established a beachhead by exploiting a public-facing server to drop a web shell or by baiting a user into resolving a lookalike domain associated with the TGR-STA-0049 campaign.

Based on research by Unit 42 2026-11-17 9 steps · 3 queries T1190 T1204.002 T1505.003 T1566

Brief

The Threat Unit

42 research titled "QUIC and Covert: Novel HTTP/3-Powered RATs Target Southeast Asian Governments" details an espionage campaign by TGR-STA-0049. This adversary targets government entities through public-facing server exploitation and phishing. They use custom tools like KUKURAT that use HTTP/3 to evade detection and maintain a long-term presence within victim networks.

How the Hunt Flows

The hunt starts by scoping the environment to find relevant infrastructure. The first query identifies hosts running web or mail services like Microsoft Exchange, IIS, Apache, and Nginx. This step focuses the investigation on systems with the highest exposure to external exploitation and ensures we are not wasting resources on low-risk assets. Two tracks of evidence gathering run in parallel after scoping. The first track monitors the identified servers for the creation of new ASPX files in sensitive directories such as \inetpub\wwwroot. The query filters for files appearing on only one or two hosts across the entire fleet. This allows the hunt to find stealthy web shells that use non-standard filenames to avoid signature-based detection. The second track examines DNS activity for resolutions of campaign-specific domains. We use indicators like www.wkuyda.com and www.thailisting.net to find hosts interacting with phishing infrastructure. Because these domains are unique to the campaign, any resolution indicates a likely compromise or interaction with a decoy. An agent triages the findings by correlating server file drops and workstation DNS hits. It evaluates the context, such as the process responsible for the DNS resolution or the location of the file creation, to determine if the activity is malicious. This process provides a clear verdict per host, allowing an analyst to confirm the breach. This activity is a hunt because it relies on prevalence and scoping rather than simple alerts. A standard detection for every new ASPX file would create excessive noise. By focusing on rare files on high-risk servers, we find the outliers that indicate a successful breach.

Blind Spots

The hunt cannot see DNS traffic if the host uses encrypted resolvers like DNS-over-HTTPS. Organizations should consider blocking outbound DoH to ensure visibility into these resolutions. The hunt also misses web shells if the adversary uses a filename that is already common across the fleet, though this is rare in targeted initial access.

In this series

Steps

  1. Scope web and Exchange servers

    Query · scoping

    Narrow the hunt to servers running software targeted for web shell exploitation.

    reads hb_software_inventorysql
    SELECT DISTINCT device_hostname FROM hb_software_inventory WHERE (LOWER(package_name) LIKE '%exchange%' OR LOWER(package_name) LIKE '%iis%' OR LOWER(package_name) LIKE '%apache%' OR LOWER(package_name) LIKE '%nginx%') AND asset_scope = 'endpoint'

    What a hit looks like. A list of hosts running web or mail services. Silence means no such software is indexed.

  2. Rare ASPX file creation

    Query · baseline

    Find web shells by identifying ASPX files created in sensitive directories that are rare across the fleet.

    reads hb_file_activitysql
    SELECT LOWER(file_path) as path, process_name, COUNT(DISTINCT device_hostname) as host_count, MIN(time) as first_seen FROM hb_file_activity WHERE activity_id = 1 AND LOWER(file_path) LIKE '%.aspx' AND (LOWER(file_path) LIKE '%\\inetpub\\wwwroot\\%' OR LOWER(file_path) LIKE '%\\front-end\\owa\\%') AND time >= datetime('now', '-{{lookback_days}} days') AND ('{{scope_hosts}}' = '' OR instr(',' || '{{scope_hosts}}' || ',', ',' || device_hostname || ',') > 0) GROUP BY 1, 2 HAVING host_count <= 2

    What a hit looks like. A file path and process name appearing on only one or two hosts. Silence means no rare ASPX creations were detected in web paths.

  3. DNS resolutions of lookalike domains

    Query · enrichment

    Identify workstations interacting with domains identified as TGR-STA-0049 phishing infrastructure.

    reads hb_dns_activitysql
    SELECT device_hostname, query_hostname, process_name, time FROM hb_dns_activity WHERE instr(',' || '{{lookalike_domains}}' || ',', ',' || LOWER(query_hostname) || ',') > 0 AND time >= datetime('now', '-{{lookback_days}} days')

    What a hit looks like. Hosts resolving malicious domains, likely from a browser or mail client. Silence means no recorded interaction.

  4. Evaluate infection evidence

    Agent triage

    Correlate server scoping with the leads to determine if a successful compromise occurred.

  5. Route on verdict

    Decision

    Direct the workflow based on the agent's findings.

  6. Isolate host

    Response action

    Contain the threat actor's initial access point.

  7. Forensic review

    Analyst task

    Manually confirm the malicious nature of the artifacts found.

  8. Close out report

    Analyst task

    Document findings and negative results.

Coverage

Scenario coverage

StageCoveredHow, or why not
Server Exploitation and Phishing
T1190 · T1505.003 · T1566
Yes identify-vulnerable-servers, rare-webshell-creations, phishing-domain-resolutions
Execution via Sideloading and RAT Deployment
T1574.002 · T1218 · T1059.001
Out of scope Belongs to another part of the 'QUIC and Covert: Novel HTTP/3-Powered RATs Target Southeast Asian Governments' series.
Defense Evasion and Heuristic Camouflage
T1055 · T1572
Out of scope Belongs to another part of the 'QUIC and Covert: Novel HTTP/3-Powered RATs Target Southeast Asian Governments' series.
HTTP/3 QUIC Command and Control
T1071 · T1572
Out of scope Belongs to another part of the 'QUIC and Covert: Novel HTTP/3-Powered RATs Target Southeast Asian Governments' series.
Discovery and Lateral Movement
T1018 · T1021.002 · T1047
Out of scope Belongs to another part of the 'QUIC and Covert: Novel HTTP/3-Powered RATs Target Southeast Asian Governments' series.
Exfiltration and Credential Collection
T1003.001 · T1056.001 · T1041
Out of scope Belongs to another part of the 'QUIC and Covert: Novel HTTP/3-Powered RATs Target Southeast Asian Governments' series.

Blind spots

  • Needs hb_dns_activity on workstations. Attackers using DNS-over-HTTPS would bypass the hb_dns_activity surface entirely. It would answer Did the host resolve the lookalike domain using a non-standard or encrypted resolver?. Remediation: Block outbound DoH at the firewall and enforce internal resolvers.
  • Needs hb_file_activity with file content analysis. A web shell with a benign filename would only be caught by the prevalence logic; manual code review is needed for confirmation. It would answer Is the new ASPX file a legitimate administrative tool or a web shell?. Remediation: Implement FIM on sensitive web server directories.

Parameters & data

Parameters

ParameterTypeDefaultWhat it is
lookalike_domainslist[domain]www.wkuyda.com, www.thailisting.net, www.yangon.it.comLookalike domains observed in phishing decoys.
lookback_daysnumber14Days of history to examine.
scope_hostslist[host]—Specific hostnames to focus on; leave empty to search the whole estate.

Telemetry

SourceCategoryTelemetry
Endpoint telemetry (hb_ surfaces)endpointendpoint

Source

Download hunt.md Definition (JSON) An open hunt.md file; it runs anywhere that reads the format.
---
analysis: This hunt combines infrastructure scoping with a behavioral prevalence baseline
  of web directories, correlating rare file drops with network IOCs. A single rule
  would alert on Suo5 filenames; this hunt identifies Suo5 even if renamed, by focusing
  on the rarity of the creation event in the context of scoped servers.
blind_spots:
- id: no-dns-visibility
  owner: Network Engineering
  question: Did the host resolve the lookalike domain using a non-standard or encrypted
    resolver?
  remediation: Block outbound DoH at the firewall and enforce internal resolvers.
  requires: hb_dns_activity on workstations
  risk: Attackers using DNS-over-HTTPS would bypass the hb_dns_activity surface entirely.
  stage: initial-access-exploitation-phishing
- id: webshell-obfuscation
  owner: Security Operations
  question: Is the new ASPX file a legitimate administrative tool or a web shell?
  remediation: Implement FIM on sensitive web server directories.
  requires: hb_file_activity with file content analysis
  risk: A web shell with a benign filename would only be caught by the prevalence
    logic; manual code review is needed for confirmation.
  stage: initial-access-exploitation-phishing
coverage:
- stage: initial-access-exploitation-phishing
  status: covered
  steps:
  - identify-vulnerable-servers
  - rare-webshell-creations
  - phishing-domain-resolutions
- reason: 'Belongs to another part of the ''QUIC and Covert: Novel HTTP/3-Powered
    RATs Target Southeast Asian Governments'' series.'
  stage: execution-sideloading-rat-deployment
  status: out_of_scope
- reason: 'Belongs to another part of the ''QUIC and Covert: Novel HTTP/3-Powered
    RATs Target Southeast Asian Governments'' series.'
  stage: defense-evasion-stealth-and-camouflage
  status: out_of_scope
- reason: 'Belongs to another part of the ''QUIC and Covert: Novel HTTP/3-Powered
    RATs Target Southeast Asian Governments'' series.'
  stage: command-and-control-http3-quic
  status: out_of_scope
- reason: 'Belongs to another part of the ''QUIC and Covert: Novel HTTP/3-Powered
    RATs Target Southeast Asian Governments'' series.'
  stage: discovery-and-lateral-movement
  status: out_of_scope
- reason: 'Belongs to another part of the ''QUIC and Covert: Novel HTTP/3-Powered
    RATs Target Southeast Asian Governments'' series.'
  stage: exfiltration-and-collection
  status: out_of_scope
guardrails:
  claims: no_unsupported
  evidence: citation_required
  missing_data: not_benign
  telemetry: untrusted
hunt:
  applicability: campaign-specific
  handoff: keep-as-periodic-hunt
  justification: TGR-STA-0049 is a sophisticated actor targeting government entities;
    early detection of their initial access vectors is vital to prevent multi-stage
    espionage and data theft.
  methodology: model-assisted
  trigger: intel-report
hypothesis: An intruder has established a beachhead by exploiting a public-facing
  server to drop a web shell or by baiting a user into resolving a lookalike domain
  associated with the TGR-STA-0049 campaign.
labels:
- hunt
- attack.t1190
- attack.t1505.003
- attack.t1566
- attack.t1204.002
- collection
- command and control
- defense evasion
- execution
- initial access
- lateral movement
name: TGR-STA-0049 Initial Access via Exploitation and Phishing
parameters:
  lookalike_domains:
    default:
    - www.wkuyda.com
    - www.thailisting.net
    - www.yangon.it.com
    description: Lookalike domains observed in phishing decoys.
    from:
      kind: article
      observed: '2026-11-16'
      ref: unit42-tgr-sta-0049
    type: list[domain]
  lookback_days:
    default: '14'
    description: Days of history to examine.
    type: number
  scope_hosts:
    default: []
    description: Specific hostnames to focus on; leave empty to search the whole estate.
    type: list[host]
provenance:
  authors:
  - name: Huntbase hunt generation
    org: huntbase.io
  generated:
    by: huntbase-hunt-generation
    from: https://unit42.paloaltonetworks.com/custom-rats-target-southeast-asia-governments/
    gates:
    - dry-run
    - lint
    - critic
    model: hb_google/gemini-3-flash-preview
rationale: The hunt begins with a scoping query on hb_software_inventory to identify
  public-facing web infrastructure. Phishing activity is searched estate-wide.
references:
- name: "Unit 42 \u2014 QUIC and Covert: Novel HTTP/3-Powered RATs Target Southeast\
    \ Asian Governments"
  url: https://unit42.paloaltonetworks.com/custom-rats-target-southeast-asia-governments/
related:
- hunt: tgr-sta-0049-execution-and-persistence
  reason: Once a beachhead is confirmed, the next phase is tracking RAT deployment
    and sideloading.
  relation: follows
scenario:
  stages:
  - name: Server Exploitation and Phishing
    observables:
    - ASPXSpy, Godzilla, Bysunue.aspx, or Suo5 web shells on Exchange or web servers
    - Decoy PDF documents targeting government sectors
    - 'Lookalike domains: www.wkuyda.com, www.thailisting.net, www.yangon.it.com'
    slug: initial-access-exploitation-phishing
    tactic: initial-access
    techniques:
    - T1190
    - T1505.003
    - T1566
  - name: Execution via Sideloading and RAT Deployment
    observables:
    - DLL side-loading of modified legitimate binaries
    - XOR-encrypted shellcode embedded in payloads
    - PerfectPioneer RAT (Go-based)
    - KUKURAT modular agent
    - Decoy installers
    slug: execution-sideloading-rat-deployment
    tactic: execution
    techniques:
    - T1574.002
    - T1218
    - T1059.001
  - name: Defense Evasion and Heuristic Camouflage
    observables:
    - KUKURAT heuristic camouflage engine generating synthetic baseline noise
    - PerfectPioneer isDangerousCommand validation engine
    - Process injection commands (process_inject)
    - UAC bypass modules
    slug: defense-evasion-stealth-and-camouflage
    tactic: defense-evasion
    techniques:
    - T1055
    - T1572
  - name: HTTP/3 QUIC Command and Control
    observables:
    - HTTP/3 over UDP port 443
    - Hashed C2 URL endpoints (e.g., /c8a4e192)
    - 'C2 Domains: ads-edge.com, www.maui-cocktailbar.com, www.cloudflacecdn.com,
      www.police.gr.com, www.investigationj6.com, www.sacofficegov.com'
    slug: command-and-control-http3-quic
    tactic: command-and-control
    techniques:
    - T1071
    - T1572
  - name: Discovery and Lateral Movement
    observables:
    - MyPsExec.dll module
    - SmbBrute.dll module
    - Async port and host scanning modules (portscan, hostscan)
    - WMI command execution (ComExec.dll)
    slug: discovery-and-lateral-movement
    tactic: lateral-movement
    techniques:
    - T1018
    - T1021.002
    - T1047
  - name: Exfiltration and Credential Collection
    observables:
    - BofLoader.dll for Beacon Object File execution
    - Keylogger module activity
    - LSASS memory access for credential harvesting
    - File upload/download activity (file_upload, file_download)
    - Screenshot module
    slug: exfiltration-and-collection
    tactic: collection
    techniques:
    - T1003.001
    - T1056.001
    - T1041
  summary: TGR-STA-0049 is a Southeast Asian espionage campaign deploying custom Go-based
    RATs (PerfectPioneer and KUKURAT) via server exploitation and phishing. The campaign
    features early adoption of HTTP/3 (QUIC) for command and control and an automated
    heuristic camouflage engine designed to blend malicious endpoint activity into
    a baseline of synthetic noise.
series:
  index: 1
  slug: quic-and-covert-novel-http-3-powered-rats-target-southeast-asian-governments
  title: 'QUIC and Covert: Novel HTTP/3-Powered RATs Target Southeast Asian Governments'
  total: 2
severity: high
targets:
  analyst:
    name: Tier-2 analyst
    role: analyst
  endpoint:
    category: endpoint
    name: Endpoint telemetry (hb_ surfaces)
    telemetry:
    - endpoint
  hunter:
    agent: true
    name: Hunt agent
tlp: clear
type: investigation
---


# TGR-STA-0049 Initial Access via Exploitation and Phishing

This hunt targets the initial access phase of the TGR-STA-0049 (PerfectPioneer/KUKURAT) campaign. It uses a dual-track approach to identify indicators of compromise: first, it identifies web and Exchange servers to monitor for rare ASPX file creations indicative of web shells like Godzilla or Suo5. Second, it monitors for DNS resolutions of lookalike domains used in phishing. An agent then correlates these signals to identify successful breaches.

## identify-vulnerable-servers
<!-- Scope web and Exchange servers -->
Narrow the hunt to servers running software targeted for web shell exploitation.

```sqlite target=endpoint role=scoping
~~~yaml
expected: A list of hosts running web or mail services. Silence means no such software
  is indexed.
reads:
- device_hostname
- package_name
silence: not_evidence_of_absence
source: hb_software_inventory
verified: dry-run
verified_at: '2026-11-17'
~~~
SELECT DISTINCT device_hostname FROM hb_software_inventory WHERE (LOWER(package_name) LIKE '%exchange%' OR LOWER(package_name) LIKE '%iis%' OR LOWER(package_name) LIKE '%apache%' OR LOWER(package_name) LIKE '%nginx%') AND asset_scope = 'endpoint'
```

## lead-fan-out
<!-- Parallel evidence gathering -->
parallel:
- → rare-webshell-creations
- → phishing-domain-resolutions
join: → agent-triage

## rare-webshell-creations
<!-- Rare ASPX file creation -->
Find web shells by identifying ASPX files created in sensitive directories that are rare across the fleet.

```sqlite target=endpoint role=baseline params=(lookback_days=lookback_days, scope_hosts=scope_hosts)
~~~yaml
baseline:
  compare: first_seen
  window: '{{lookback_days}}d'
expected: A file path and process name appearing on only one or two hosts. Silence
  means no rare ASPX creations were detected in web paths.
prevalence:
  by: device_hostname
  key:
  - file_path
  - process_name
  rare_below: 3
reads:
- file_path
- process_name
- device_hostname
- time
silence: not_evidence_of_absence
source: hb_file_activity
verified: dry-run
verified_at: '2026-11-17'
~~~
SELECT LOWER(file_path) as path, process_name, COUNT(DISTINCT device_hostname) as host_count, MIN(time) as first_seen FROM hb_file_activity WHERE activity_id = 1 AND LOWER(file_path) LIKE '%.aspx' AND (LOWER(file_path) LIKE '%\\inetpub\\wwwroot\\%' OR LOWER(file_path) LIKE '%\\front-end\\owa\\%') AND time >= datetime('now', '-{{lookback_days}} days') AND ('{{scope_hosts}}' = '' OR instr(',' || '{{scope_hosts}}' || ',', ',' || device_hostname || ',') > 0) GROUP BY 1, 2 HAVING host_count <= 2
```

## phishing-domain-resolutions
<!-- DNS resolutions of lookalike domains -->
Identify workstations interacting with domains identified as TGR-STA-0049 phishing infrastructure.

```sqlite target=endpoint role=enrichment params=(lookback_days=lookback_days, lookalike_domains=lookalike_domains)
~~~yaml
expected: Hosts resolving malicious domains, likely from a browser or mail client.
  Silence means no recorded interaction.
reads:
- device_hostname
- query_hostname
- process_name
- time
silence: not_evidence_of_absence
source: hb_dns_activity
verified: dry-run
verified_at: '2026-11-17'
~~~
SELECT device_hostname, query_hostname, process_name, time FROM hb_dns_activity WHERE instr(',' || '{{lookalike_domains}}' || ',', ',' || LOWER(query_hostname) || ',') > 0 AND time >= datetime('now', '-{{lookback_days}} days')
```

## agent-triage
<!-- Evaluate infection evidence -->
```agent target=hunter
cite: required
context:
- identify-vulnerable-servers
- rare-webshell-creations
- phishing-domain-resolutions
max_iterations: 5
objective: Determine if the rare ASPX creations on scoped servers or the lookalike
  domain resolutions on workstations indicate a successful TGR-STA-0049 breach.
success_criteria: A verdict per host citing specific rows and indicators.
tools:
- endpoint
```

## verdict-decision
<!-- Route on verdict -->
if~: "The triage verdict is malicious for at least one host based on confirmed web shell creation or high-confidence phishing callback." (confidence: high, judge=hunter)
then: → isolate-beachhead
indeterminate: → analyst-forensic-review
unavailable: → analyst-forensic-review (blind_spot: no-dns-visibility)
else: → close-out-report

## isolate-beachhead
<!-- Isolate host -->
```action target=endpoint
~~~yaml
approval: required
~~~
Isolate the compromised server or workstation immediately to prevent lateral movement.
```
→ analyst-forensic-review

## analyst-forensic-review
<!-- Forensic review -->
```manual target=analyst
Inspect the .aspx files identified on the server; check for Suo5 or Godzilla signatures. For phishing, retrieve and examine decoy PDFs if available in browser cache or mail downloads.
```
→ close-out-report

## close-out-report
<!-- Close out report -->
```manual target=analyst
Record the scoped hosts and the DNS results. If malicious activity was found, pivot to the RAT deployment hunt.
```
→ end

Run it

Take this hunt into your environment.

Open it in Huntbase to run every step against your own connections, with Scout weighing the evidence and your analysts in command. Or take the open hunt.md file anywhere that reads the format.

Machine-drafted by huntbase-hunt-generation using hb_google/gemini-3-flash-preview, gated by dry-run, lint, critic, then reviewed by a person.

Locked pack

Sign up to unlock

Pack contents are available to Huntbase users.