Possible Residential Proxyware Beacon to PacketSDK Infrastructure

PremiumReviewedSigma · Medium · v1
Product
windows
Category
dns_query
Author
HuntRule
Published
2026-10-11
Updated
2026-10-11

ATT&CK techniques

C2
  1. Recon

  2. Resource Dev

  3. Initial Access

  4. Execution

  5. Persistence

  6. Priv Esc

  7. Defense Evasion

  8. Cred Access

  9. Discovery

  10. Lateral Movement

  11. Collection

  12. Exfiltration

  13. Impact

What it detects

This rule detects DNS lookups for proxyware SDK command infrastructure such as packetsdk and hexsdk and castarsdk domains used by residential proxy networks. Such beacons indicate a host has been enrolled as a proxy exit node without authorization.

Related detections9 linkedT1071.001 — drag to rearrange
Possible GhostContainer Exchange Backdoor C2 Request via OWA (via webserver)
Malicious AdaptixC2 Beacon via X-Beacon-Id Header and Default User Agent (via proxy)
Possible JanelaRAT C2 Beacon via Structured HTTP Query (via proxy)
Suspicious StupidSandwichAgent User-Agent in C2 Traffic by StaryDobry
Suspicious CanesSpy WhatsApp Mod C2 Beacon to AllRequest Endpoint (via proxy)
Suspicious PowerShell WebClient UploadString Network Beacon
Suspicious PipeMagic Named Pipe Creation (via pipe_created)
Suspicious UUID Named Pipe Created Consistent with Mythic SMB Agent
Suspicious RuntimeBroker Network Connection via Loki Mythic Agent
Possible Residential Proxyware Beacon to PacketSDK Infrastructure
Pivot detection · T1071.001 · 9 related

Detection content is published as a reviewed draft. Tune thresholds and exclusions against your own telemetry before enabling this rule for alerting.