Suspicious TeamPCP antv GitHub Commit Search C2 Trigger firedalazer (via proxy)

PremiumReviewedSigma · Medium · v1
Category
proxy
Author
HuntRule
Published
2026-11-05
Updated
2026-11-05

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 GitHub commit search API requests carrying the firedalazer trigger token which the TeamPCP @antv backdoor polls as a dead-drop command-and-control channel over a legitimate web service. Use of GitHub search as a covert C2 with this specific query string indicates an active implant awaiting operator instructions.

Related detections9 linkedT1102 — drag to rearrange
Possible PowerShell Empire Default C2 URI Beaconing
Suspicious Network Connection from mspaint or msiexec (via network_connection)
Possible Discord Webhook C2 or Data Exfiltration
Possible Gamaredon C2 via Ephemeral Tunneling and Worker Services
Possible Gamaredon Dead-Drop C2 via Telegraph and GoFile Web Services
Suspicious APT29 Zulip C2 Communication via curl User-Agent (via proxy)
Possible Telegram API Command and Control DNS Query
Malicious Anubis Ransomware Cloudflare Tunnel via cloudflared (via process_creation)
Possible ITG05 Headlace Staging via Mocky and Mockbin Services (via proxy)
Suspicious TeamPCP antv GitHub Commit Search C2 Trigger firedalazer (via proxy)
Pivot detection · T1102 · 9 related

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