Possible Spectre Ops C2 Beacon via nico and yfat Query Parameters via proxy

PremiumReviewedSigma · High · v1
Category
proxy
Author
HuntRule
Published
2026-10-17
Updated
2026-10-17

ATT&CK techniques

Cred Access → C2
  1. Recon

  2. Resource Dev

  3. Initial Access

  4. Execution

  5. Persistence

  6. Priv Esc

  7. Defense Evasion

  8. Discovery

  9. Lateral Movement

  10. Collection

  11. Exfiltration

  12. Impact

What it detects

This rule detects Spectre Ops stealer command and control traffic that posts to a PHP endpoint carrying the distinctive nico and yfat query parameters. These custom parameter names carry stolen data and bot identifiers to the panel. The parameter pairing uniquely fingerprints the exfiltration channel independent of the C2 host or the nonstandard port.

Related detections9 linkedT1071.001 — drag to rearrange
Suspicious Data Exfiltration Channel to Telegram or Discord via dns_query
Possible Origin Logger C2 Exfiltration via Hardcoded User Agent and Gate Endpoints via proxy
Possible ZharkBot C2 Beacon via socket Endpoint with Bot Parameters via proxy
Suspicious Browser Kiosk Mode Forcing Credential Entry via process_creation
Malicious Live Ledger Stealer Execution via Ledger Lives Masquerade via process_creation
Malicious Dropbox Cloud C2 via Spoofed Googlebot User Agent
Possible FluBot C2 Polling via Known Malware URI Paths
Malicious MetaStealer C2 via cpp-httplib User-Agent (via proxy)
Possible Cobalt Strike Beacon URI Pattern via Web C2
Possible Spectre Ops C2 Beacon via nico and yfat Query Parameters via proxy
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.