Skip to content
COOEY
LIVE · 0m

◄ SITREP

TRIAGE & INVESTIGATION

SECOPS

Security-ops queue over the live fused alert streams — probe/outage verdicts & IOC/attack events, severity-ranked. Select an alert to investigate: raw payload, telemetry, outage-vs-vantage verification, and IOC enrichment. Read-only console; escalation/isolation is the private incident plane.

Alert queue
350
active alerts
Critical
96
top-priority
High
181
elevated
Under investigation
SIG-FPURQ4
FEODO C2 case
ALERT_QUEUE
sev · source · verdict live
CRITICAL FEODO C2 12s
LIVE C2: 50.16.16.211:443 (QakBot)
CRITICAL FEODO C2 12s
LIVE C2: 50.16.16.211:443 (QakBot)
CRITICAL C2INTEL 13m
Cobaltstrike: 101.43.103.154
CRITICAL C2INTEL 13m
Cobaltstrike: 101.43.103.154
CRITICAL C2INTEL 13m
Cobaltstrike: 101.42.255.92
CRITICAL C2INTEL 13m
Cobaltstrike: 101.42.255.92
CRITICAL C2INTEL 13m
Cobaltstrike: 101.33.225.32
CRITICAL C2INTEL 13m
Cobaltstrike: 101.33.225.32
CRITICAL C2INTEL 13m
Cobaltstrike: 101.200.193.211
CRITICAL C2INTEL 13m
Cobaltstrike: 101.200.193.211
CRITICAL C2INTEL 14m
Cobaltstrike: 101.133.229.117
CRITICAL C2INTEL 14m
Cobaltstrike: 101.133.229.117
CRITICAL C2INTEL 14m
Cobaltstrike: 101.126.10.34
CRITICAL C2INTEL 14m
Cobaltstrike: 101.126.10.34
CRITICAL C2INTEL 14m
Cobaltstrike: 1.15.76.39
CRITICAL C2INTEL 14m
Cobaltstrike: 1.15.76.39
CRITICAL DEFCON 14m
[DEFCON 2] DDoS Origin + Active Threat Feed Signal
CRITICAL DEFCON 28m
[DEFCON 1] Nation-State Network Activity
CRITICAL FEODO C2 30m
LIVE C2: 50.16.16.211:443 (QakBot)
CRITICAL IODA 46m
NAYATEL-PK -- Punjab — ping-slash24 critical
CRITICAL IODA 46m
INTERNETBOLAGET -- Sweden — ping-slash24 critical
CRITICAL IODA 46m
NAYATEL-PK -- Punjab — ping-slash24 critical
CRITICAL IODA 46m
INTERNETBOLAGET -- Sweden — ping-slash24 critical
CRITICAL DEFCON 46m
[DEFCON 2] DDoS Origin + Active Threat Feed Signal
CRITICAL DEFCON 48m
DigitalOcean — Monitoring — Cloud Control Panel and API
CRITICAL IODA 56m
AS49531 (NETCOM-R-AS) — ping-slash24 critical
CRITICAL IODA 56m
NETCOM-R-AS -- Russian Federation — ping-slash24 critical
CRITICAL IODA 56m
NETCOM-R-AS -- Moskva — ping-slash24 critical
CRITICAL IODA 56m
NETCOM-R-AS -- Russian Federation — ping-slash24 critical
CRITICAL IODA 56m
NETCOM-R-AS -- Moskva — ping-slash24 critical
CRITICAL IODA 56m
AS49531 (NETCOM-R-AS) — ping-slash24 critical
CRITICAL IODA 56m
AS49531 (NETCOM-R-AS) — ping-slash24 critical
CRITICAL IODA 56m
NETCOM-R-AS -- Russian Federation — ping-slash24 critical
CRITICAL IODA 56m
NETCOM-R-AS -- Moskva — ping-slash24 critical
CRITICAL IODA 56m
NETCOM-R-AS -- Russian Federation — ping-slash24 critical
CRITICAL IODA 56m
NETCOM-R-AS -- Moskva — ping-slash24 critical
CRITICAL IODA 56m
AS49531 (NETCOM-R-AS) — ping-slash24 critical
CRITICAL FEODO C2 1h
LIVE C2: 50.16.16.211:443 (QakBot)
CRITICAL IODA 1h
TCI -- Alborz — ping-slash24 critical
CRITICAL IODA 1h
TCI -- Alborz — ping-slash24 critical
CRITICAL IODA 1h
TCI -- Alborz — ping-slash24 critical
CRITICAL IODA 1h
TCI -- Alborz — ping-slash24 critical
CRITICAL IODA 1h
TCI -- Alborz — ping-slash24 critical
CRITICAL IODA 1h
TCI -- Alborz — ping-slash24 critical
CRITICAL IODA 1h
TCI -- Alborz — ping-slash24 critical
CRITICAL IODA 1h
TCI -- Alborz — ping-slash24 critical
CRITICAL IODA 1h
TCI -- Alborz — ping-slash24 critical
CRITICAL IODA 1h
TCI -- Alborz — ping-slash24 critical
CRITICAL C2INTEL 1h
Cobaltstrike: 101.43.103.154
CRITICAL C2INTEL 1h
Cobaltstrike: 101.42.255.92
CRITICAL C2INTEL 1h
Cobaltstrike: 101.33.225.32
CRITICAL C2INTEL 1h
Cobaltstrike: 101.200.193.211
CRITICAL C2INTEL 1h
Cobaltstrike: 101.133.229.117
CRITICAL C2INTEL 1h
Cobaltstrike: 101.126.10.34
CRITICAL C2INTEL 1h
Cobaltstrike: 1.15.76.39
CRITICAL IODA 1h
EMPIRE-40545 -- United States — ping-slash24 critical
CRITICAL IODA 1h
SYNAPSE -- Japan — ping-slash24 critical
CRITICAL IODA 1h
EMPIRE-40545 -- United States — ping-slash24 critical
CRITICAL IODA 1h
SYNAPSE -- Japan — ping-slash24 critical
CRITICAL IODA 1h
SYNAPSE -- Japan — ping-slash24 critical
CRITICAL IODA 1h
EMPIRE-40545 -- United States — ping-slash24 critical
CRITICAL IODA 1h
EMPIRE-40545 -- United States — ping-slash24 critical
CRITICAL IODA 1h
SYNAPSE -- Japan — ping-slash24 critical
CRITICAL IODA 1h
EMPIRE-40545 -- United States — ping-slash24 critical
CRITICAL IODA 1h
SYNAPSE -- Japan — ping-slash24 critical
CRITICAL IODA 1h
SYNAPSE -- Japan — ping-slash24 critical
CRITICAL IODA 1h
EMPIRE-40545 -- United States — ping-slash24 critical
CRITICAL DEFCON 1h
[DEFCON 2] DDoS Origin + Active Threat Feed Signal
CRITICAL DEFCON 1h
[DEFCON 1] Nation-State Network Activity
CRITICAL IODA 1h
AS58466 (CT-Guangzhou-IDC) — bgp critical
CRITICAL IODA 1h
AS58466 (CT-Guangzhou-IDC) — bgp critical
CRITICAL FEODO C2 1h
LIVE C2: 50.16.16.211:443 (QakBot)
CRITICAL IODA 1h
AS134176 (RAIBOW-AS-AP) — bgp critical
CRITICAL IODA 1h
AS134176 (RAIBOW-AS-AP) — bgp critical
CRITICAL IODA 1h
AS134176 (RAIBOW-AS-AP) — bgp critical
CRITICAL IODA 1h
NBLNETWORKS-AS -- Finland — ping-slash24 critical
CRITICAL IODA 1h
NBLNETWORKS-AS -- Finland — ping-slash24 critical
CRITICAL IODA 1h
ORLANDOTELCO -- United States — ping-slash24 critical
CRITICAL IODA 2h
GSNU-AS-KR -- South Korea — ping-slash24 critical
CRITICAL IODA 2h
GSNU-AS-KR -- South Korea — ping-slash24 critical
INVESTIGATION
Investigation ID
SIG-FPURQ4
Status
C2 SERVER
CRITICAL FEODO C2 · US 12s ago
Raw payload
LIVE C2: 50.16.16.211:443 (QakBot) Active QakBot C2 — AS14618 AMAZON-AES — US. Online since 2025-12-30 13:56:31 (238d). Last confirmed: 2026-03-12.
Telemetry timeline · related activity
10:15:55Z
LIVE C2: 50.16.16.211:443 (QakBot)
09:45:55Z
LIVE C2: 50.16.16.211:443 (QakBot)
09:15:55Z
LIVE C2: 50.16.16.211:443 (QakBot)
↗ US probes ↗ AS14618 routing ↗ 50.16.16.211 on map ↗ signal fusion
Escalate / isolate actions live in the private incident plane (per-tenant).
IOC_ENRICHMENT
50.16.16.211 4/91
⚠ Malicious activity detected
Detections · 5 engines
Chong Lua Dao malicious
CRDF malicious
CyRadar malicious
G-Data malware
Gridinsoft suspicious
GEOUS
NETWORK50.16.0.0/15
VirusTotal ▸