Skip to content
skopnix
← Sigma detections

Sigma · Actor indicator sweep

ShinyHunters IP indicators

severity
high
confidence
92/100
generated
18 Nov 2026
Linked actors
ShinyHunters

1 IP indicator skopnix attributes to ShinyHunters, each backed by threat-feed evidence (see the FP-safety notes for the exact counts).

False-positive notes

1 indicator. Evidence: 1 listed by 2 or more independent non-scanner feed publishers. Listed by 3 independent sources in all. Newest feed sighting 2026-11-13, oldest 2026-11-13 (a live actor sweep accepts at most 90 days). Screened against reserved space, public known-good lists (CDN / cloud / scanners / top sites), internet-noise reputation when enriched, and sinkhole address lists. Re-validate against last_seen before blocking: infrastructure is re-assigned.

References

title: Skopnix - ShinyHunters IP indicatorsid: 2e8ee417-d307-505a-8332-49de3b8fbf86status: experimentaldescription: 1 IP indicator skopnix attributes to ShinyHunters, each backed by threat-feed evidence (see the FP-safety notes for the exact counts).references:  - https://skopnix.com/actors/shinyhuntersauthor: skopnixdate: '2026-11-18'tags:  - attack.command-and-control  - attack.t1071logsource:  category: firewalldetection:  selection:    dst_ip:      - 176.120.22.24  condition: selectionfalsepositives:  - Legitimate services sharing the address; verify against skopnix confidence + last_seenlevel: high

skopnix-sigma-actor-shinyhunters-ip-cc34893b.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.