← Sigma detections
Sigma · Indicator
Traffic to known malicious IP 177.10.160.46
- severity
- medium
- confidence
- 100/100
- generated
- 19 Nov 2026
Connection to an IP tracked by skopnix as malicious infrastructure.
False-positive notes
Scoped to one indicator with skopnix confidence 100/100 from 12 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 2 independent non-scanner sources, seen within the last 90 days. Re-validate against last_seen before blocking: infrastructure is re-assigned.
References
title: Skopnix - Traffic to known malicious IP 177.10.160.46id: e4202950-6334-5e63-b550-614ad44830d3status: experimentaldescription: Connection to an IP tracked by skopnix as malicious infrastructure.references: - https://skopnix.com/ioc/177.10.160.46author: skopnixdate: '2026-11-19'tags: - attack.command-and-control - attack.t1071logsource: category: firewalldetection: selection: dst_ip: 177.10.160.46 condition: selectionfalsepositives: - Legitimate services sharing the address; verify against skopnix confidence + last_seenlevel: mediumskopnix-sigma-ioc-ip-177-10-160-46-0ad5ddd9.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.