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
473
active alerts
Critical
77
top-priority
High
166
elevated
Under investigation
SIG-6L786A
IODA case
ALERT_QUEUE
sev · source · verdict live
CRITICAL C2INTEL 11m
Cobaltstrike: 101.126.10.34
CRITICAL C2INTEL 11m
Cobaltstrike: 101.126.10.34
CRITICAL C2INTEL 17m
Cobaltstrike: 1.15.76.39
CRITICAL FEODO C2 34m
LIVE C2: 50.16.16.211:443 (QakBot)
CRITICAL C2INTEL 1h
Cobaltstrike: 101.33.225.32
CRITICAL C2INTEL 1h
Cobaltstrike: 101.201.103.158
CRITICAL FEODO C2 1h
LIVE C2: 50.16.16.211:443 (QakBot)
CRITICAL C2INTEL 1h
Cobaltstrike: 101.200.193.211
CRITICAL C2INTEL 1h
Cobaltstrike: 101.133.229.117
CRITICAL C2INTEL 1h
Cobaltstrike: 101.133.229.117
CRITICAL DEFCON 1h
Origin AS change: 198.136.150.0/24
CRITICAL C2INTEL 1h
Cobaltstrike: 101.126.10.34
CRITICAL C2INTEL 1h
Cobaltstrike: 1.15.76.39
CRITICAL IODA 1h
AS37347 (NGCOM) — bgp critical
CRITICAL IPSUM 1h
IPsum: 195.178.110.218 (score 10/10+)
CRITICAL IPSUM 1h
IPsum: 160.250.132.238 (score 10/10+)
CRITICAL IPSUM 1h
IPsum: 160.250.132.238 (score 10/10+)
CRITICAL IPSUM 1h
IPsum: 95.85.245.227 (score 10/10+)
CRITICAL IODA 1h
AS28652 -- Brazil — ping-slash24 critical
CRITICAL IPSUM 1h
IPsum: 77.90.185.20 (score 10/10+)
CRITICAL IPSUM 1h
IPsum: 37.120.213.13 (score 10/10+)
CRITICAL IPSUM 1h
IPsum: 37.120.213.13 (score 10/10+)
CRITICAL IPSUM 1h
IPsum: 79.72.3.119 (score 11/10+)
CRITICAL IPSUM 1h
IPsum: 79.72.3.119 (score 11/10+)
CRITICAL FEODO C2 1h
LIVE C2: 50.16.16.211:443 (QakBot)
CRITICAL IPSUM 1h
IPsum: 107.150.97.10 (score 12/10+)
CRITICAL IODA 1h
AS8507 () — bgp critical
CRITICAL IODA 1h
AS8507 () — bgp critical
CRITICAL IODA 1h
AS8507 () — bgp critical
CRITICAL IODA 1h
AS8507 () — bgp critical
CRITICAL IODA 1h
AS7540 (HKCIX-AS-AP) — ping-slash24 critical
CRITICAL IODA 1h
HKCIX-AS-AP -- Hong Kong — ping-slash24 critical
CRITICAL IODA 1h
HKCIX-AS-AP -- Wan Chai — ping-slash24 critical
CRITICAL IODA 1h
HKCIX-AS-AP -- Wan Chai — ping-slash24 critical
CRITICAL IODA 1h
HKCIX-AS-AP -- Hong Kong — ping-slash24 critical
CRITICAL IODA 1h
AS7540 (HKCIX-AS-AP) — ping-slash24 critical
CRITICAL IODA 1h
HKCIX-AS-AP -- Hong Kong — ping-slash24 critical
CRITICAL IODA 1h
HKCIX-AS-AP -- Wan Chai — ping-slash24 critical
CRITICAL IODA 1h
AS268976 -- Brazil — ping-slash24 critical
CRITICAL IODA 2h
CMNET-Hunan-AP -- Guangdong — ping-slash24 critical
CRITICAL IODA 2h
CMNET-Hunan-AP -- Guangdong — ping-slash24 critical
CRITICAL IODA 2h
ORLANDOTELCO -- United States — ping-slash24 critical
CRITICAL DEFCON 2h
Mass withdrawal burst: 150 routes
CRITICAL C2INTEL 2h
Cobaltstrike: 101.33.225.32
CRITICAL FEODO C2 2h
LIVE C2: 50.16.16.211:443 (QakBot)
CRITICAL C2INTEL 2h
Cobaltstrike: 101.201.103.158
CRITICAL C2INTEL 2h
Cobaltstrike: 101.200.193.211
CRITICAL IODA 2h
CHINAMOBILE-CN -- Hunan — ping-slash24 critical
CRITICAL IODA 2h
AS9808 (CHINAMOBILE-CN) — ping-slash24 critical
CRITICAL C2INTEL 2h
Cobaltstrike: 101.133.229.117
CRITICAL C2INTEL 2h
Cobaltstrike: 101.126.10.34
CRITICAL C2INTEL 2h
Cobaltstrike: 1.94.65.9
CRITICAL IODA 2h
CHINAMOBILE-CN -- Hubei — ping-slash24 critical
CRITICAL IODA 2h
CHINAMOBILE-CN -- Chongqing — ping-slash24 critical
CRITICAL IODA 2h
AS24547 (CMNET-V4HEBEI-AS-AP) — ping-slash24 critical
CRITICAL IODA 2h
CMNET-Shanxi-AP -- Shanghai — ping-slash24 critical
CRITICAL IODA 2h
AS132510 (ShanXiMCC-IDC) — ping-slash24 critical
CRITICAL IODA 2h
AS56044 (CMNET-AS-Liaoning) — ping-slash24 critical
CRITICAL IODA 2h
AS132510 (ShanXiMCC-IDC) — ping-slash24 critical
CRITICAL IODA 2h
AS24445 (CMNET-V4henan-AS-AP) — ping-slash24 critical
CRITICAL IODA 2h
AS132510 (ShanXiMCC-IDC) — ping-slash24 critical
CRITICAL IODA 2h
CMNET-Hunan-AP -- China — ping-slash24 critical
CRITICAL IODA 2h
AS38019 (CMNET-V4TIANJIN-AS-AP) — ping-slash24 critical
CRITICAL IODA 2h
CHINAMOBILE-CN -- Gansu — ping-slash24 critical
CRITICAL IODA 2h
CMNET-Hunan-AP -- Shanghai — ping-slash24 critical
CRITICAL IODA 2h
CMNET-V4HEBEI-AS-AP -- Tianjin — ping-slash24 critical
CRITICAL IODA 2h
CMNET-V4henan-AS-AP -- China — ping-slash24 critical
CRITICAL IODA 3h
AS141739 (CT-CHONGQING-MAN2-AP) — ping-slash24 critical
CRITICAL C2INTEL 3h
Cobaltstrike: 101.200.193.211
CRITICAL DEFCON 3h
[DEFCON 2] DDoS Origin + Active Threat Feed Signal
CRITICAL DEFCON 3h
[DEFCON 1] Nation-State Network Activity
CRITICAL C2INTEL 4h
Cobaltstrike: 101.201.103.158
CRITICAL DEFCON 4h
[DEFCON 2] DDoS Origin + Active Threat Feed Signal
CRITICAL IODA 5h
AS7540 (HKCIX-AS-AP) — ping-slash24 critical
CRITICAL DEFCON 5h
[DEFCON 1] Nation-State Network Activity
CRITICAL DEFCON 5h
[DEFCON 2] DDoS Origin + Active Threat Feed Signal
CRITICAL IODA 5h
RADORE -- Turkey — ping-slash24 critical
HIGH RANSOMLOOK now
Ransomware: audit team → AUDIT ENTITY: TEK SPB
HIGH RANSOMLOOK now
Ransomware: audit team → AUDIT ENTITY: TEK SPB
HIGH RANSOMLOOK now
Ransomware: audit team → AUDIT ENTITY: st***co
INVESTIGATION
Investigation ID
SIG-6L786A
Status
OUTAGE
CRITICAL IODA · CN 2h ago
Raw payload
CHINAMOBILE-CN -- Gansu — ping-slash24 critical IODA critical outage signal on CHINAMOBILE-CN -- Gansu (China Mobile), AS9808, CN. 51 of 65 /24 blocks responding to active probes (78% of baseline, 14 /24s dark). Datasource: ping-slash24.
Telemetry timeline · related activity
14:50:00Z
CMNET-Hunan-AP -- Guangdong — ping-slash24 critical
14:50:00Z
CMNET-Hunan-AP -- Guangdong — ping-slash24 critical
14:40:00Z
CHINAMOBILE-CN -- Hunan — ping-slash24 critical
14:40:00Z
AS9808 (CHINAMOBILE-CN) — ping-slash24 critical
14:30:00Z
CHINAMOBILE-CN -- Hubei — ping-slash24 critical
14:30:00Z
CHINAMOBILE-CN -- Chongqing — ping-slash24 critical
↗ CN probes ↗ AS9808 routing ↗ signal fusion
Escalate / isolate actions live in the private incident plane (per-tenant).
IOC_ENRICHMENT
No network indicator on this alert — nothing to enrich.
Geo: CN