Traffic to known C2 IP 212.11.64.105
SIGmediumconfidence 77/100generated 2026-10-18
Connection to an IP tracked by skopnix as Coreshell C2.
- Linked actors
- UAT-9244
- False positives
- Scoped to one indicator with skopnix confidence 77/100 from 2 independent sources; checked against RFC1918/reserved space, CDN / cloud / scanner ranges and top-site lists (MISP warninglists), GreyNoise when enriched, and skopnix's benign-infrastructure list. Re-validate against last_seen before blocking: infrastructure is re-assigned.
Sigma rule
skopnix-sigma-ioc-ip-212-11-64-105-da19802d.ymldownload .yml ↓title: Skopnix - Traffic to known C2 IP 212.11.64.105
id: 8d97edcb-260e-5b25-9ff8-11404d359f6e
status: experimental
description: Connection to an IP tracked by skopnix as Coreshell C2.
references:
- https://skopnix.com/ioc/212.11.64.105
author: skopnix
date: '2026-10-18'
tags:
- attack.command-and-control
- attack.t1071
logsource:
category: firewall
detection:
selection:
dst_ip: 212.11.64.105
condition: selection
falsepositives:
- Legitimate services sharing the address; verify against skopnix confidence + last_seen
level: medium
How to deploy on Sigma
- 1.Convert for your SIEM with sigma-cli / pySigma, e.g. sigma convert -t splunk -p sysmon rule.yml.
- 2.Run it as a hunt first: every rule ships as status experimental.
- 3.Promote to an alert once a week of results is clean on your data.
Check · The processing pipeline must map the logsource (firewall, dns, proxy, webserver, process_creation) to your field names.