Possible WailingCrab MQTT C2 to Public Broker (via network_connection)

PremiumReviewedSigma · Medium · v1
Product
windows
Category
network_connection
Author
HuntRule
Published
2026-10-02
Updated
2026-10-02

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 WailingCrab command-and-control that abuses the MQTT messaging protocol by connecting to the public emqx broker on TCP port 1883. Enterprise endpoints seldom initiate MQTT sessions to this public broker. The connection carries base64-encoded command traffic.

Related detections8 linkedT1071 — drag to rearrange
Suspicious Outbound Network Connection from explorer.exe
Suspicious SSH Service on Non Standard Port 57722
Suspicious Bash Reverse Shell via /dev/tcp
Windows GitHub Self-Hosted Runner Execution via Runner.Worker and Runner.Listener
macOS Installer Scripts Spawning Suspicious Interpreter Child Processes
Windows DNS analytic events for GALLIUM-related ddns QNAMEs (EventID 257)
Windows Process Creation alerts on GALLIUM-associated hash IOCs
Windows Process Execution Matching SILENTTRINITY Stager Metadata (st2stager)
Possible WailingCrab MQTT C2 to Public Broker (via network_connection)
Pivot detection · T1071 · 8 related

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