← Sigma detections
Sigma · Indicator
DNS query for known malicious domain 5vobauua3ojpklx.icu
- severity
- high
- confidence
- 100/100
- generated
- 18 Nov 2026
DNS resolution of a domain tracked by skopnix as Coruna infrastructure.
False-positive notes
Scoped to one indicator with skopnix confidence 100/100 from 3 independent sources; checked against RFC1918/reserved space, CDN / cloud / scanner ranges and top-site lists (public known-good lists), sinkholes, internet-noise reputation when enriched, and skopnix's benign-infrastructure list. Threat-feed evidence: listed by 3 independent non-scanner sources, seen within the last 90 days. Re-validate against last_seen before blocking: infrastructure is re-assigned.
References
title: Skopnix - DNS query for known malicious domain 5vobauua3ojpklx.icuid: 70472b3c-36ff-52d1-acc6-89e76668aa22status: experimentaldescription: DNS resolution of a domain tracked by skopnix as Coruna infrastructure.references: - https://skopnix.com/ioc/5vobauua3ojpklx.icuauthor: skopnixdate: '2026-11-18'tags: - attack.command-and-control - attack.t1105logsource: category: dnsdetection: selection: query: 5vobauua3ojpklx.icu condition: selectionfalsepositives: - Legitimate services sharing the address; verify against skopnix confidence + last_seenlevel: highskopnix-sigma-ioc-domain-5vobauua3ojpklx-icu-ec3e5d75.yml
How to deploy on Sigma
- Step 1
- Convert for your SIEM with sigma-cli / pySigma, e.g. sigma convert -t splunk -p sysmon rule.yml.
- Step 2
- Run it as a hunt first: every rule ships as status experimental.
- Step 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.